You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description of problem: Use the dashboard to create a new workspace. Open the workspace in the IDE attempt to create a project from the IDE and there are no project types available in the tree on the left so you can't actually create a project.
Che version:4.0.0-beta-13-1 Che install directory:~/Downloads/eclipse-che-4.0.0-beta-13-1 Docker version:
Client:
Version: 1.10.0
API version: 1.22
Go version: go1.5.3
Git commit: 590d5108
Built: Thu Feb 4 18:18:11 2016
OS/Arch: darwin/amd64
Server:
Version: 1.10.0
API version: 1.22
Go version: go1.5.3
Git commit: 590d5108
Built: Thu Feb 4 19:55:25 2016
OS/Arch: linux/amd64
Java version:N/A I'm using che.sh run -i (so whatever you have in your container) Environment details (AWS, VirtualBox, physical, etc.):I'm on my mac using the default dockertoolbox 0.10 and default che 4.0.0-beta-13-1.
The text was updated successfully, but these errors were encountered:
When inside of a workspace, you must first create the project by selecting the source location (zip, git, github). After the project is imported, we'll do an estimation on the project to determine its project type. If we cannot determine the project type, then the project configuration wizard is loaded.
Description of problem: Use the dashboard to create a new workspace. Open the workspace in the IDE attempt to create a project from the IDE and there are no project types available in the tree on the left so you can't actually create a project.
Che version:
4.0.0-beta-13-1
Che install directory:
~/Downloads/eclipse-che-4.0.0-beta-13-1
Docker version:
Docker Info:
Java version:
N/A I'm using che.sh run -i (so whatever you have in your container)
Environment details (AWS, VirtualBox, physical, etc.):
I'm on my mac using the default dockertoolbox 0.10 and default che 4.0.0-beta-13-1.
The text was updated successfully, but these errors were encountered: