[ https://issues.jboss.org/browse/JBIDE-13769?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13769: ------------------------------------- Steps to Reproduce: # 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, try to import it a 2nd time: You have to provide a custom git clone location 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: !could-not-maven-import-null.png! was: # 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, try to import it a 2nd time: You have to provide a custom git clone location 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: !could-not-maven-import-null.png! !could-not-maven-import-null.png! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira