-
Bug
-
Resolution: Done
-
Minor
-
4.1.0.Alpha2
-
None
-
- ASSERT: make sure you have a java/maven application on OpenShift (ex. jbossas-7, jbosseap-6, springeap-6)
- EXEC: import your application to your workspace via Import-wizard
- EXEC: once it's imported, modify the pom.xml to get invalid: ex. and a "!" in front of an xml-tag.
- EXEC: commit the change and push it to OpenShift
- EXEC: once it's pushed, remove the project and re-import it.
Result:
The import starts, the cloning happens, but when the maven import is executed, the wizard reports that the maven project null could not be imported:
ASSERT: make sure you have a java/maven application on OpenShift (ex. jbossas-7, jbosseap-6, springeap-6) EXEC: import your application to your workspace via Import-wizard EXEC: once it's imported, modify the pom.xml to get invalid: ex. and a "!" in front of an xml-tag. EXEC: commit the change and push it to OpenShift EXEC: once it's pushed, remove the project and re-import it. Result: The import starts, the cloning happens, but when the maven import is executed, the wizard reports that the maven project null could not be imported: -
You cannot import an OpenShift java/maven project twice since the project name has to be unique within the very same Eclipse workspace. The OpenShift import wizard errors while importing and reports that it could not import the maven project null.
We cannot change the wizard to error before importing since we have to clone the application repo and look into the pom to find out about the name clash.
Nevertheless, we should fix the lacking error message that's missing the project name.
- relates to
-
-
- Closed
-
-
-
- Closed
-
