[
https://issues.jboss.org/browse/JBIDE-11264?page=com.atlassian.jira.plugi...
]
Andre Dietisheim updated JBIDE-11264:
-------------------------------------
Attachment: untitled.mp4
in my screencast I clone to /tmp/ which is clearly not in the workspace. The error does
not appear in this setup.
When trying with your approach, where I clone to the workspace, I could reproduce your
bug. Having a repo in the workspace root is clearly not recommended. But still, this has
to be a "bug" in the maven import process which is not in my control.
Wrong workspace project name when the OpenShift app name != artifact
id in pom file and the project location is within the workspace
------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-11264
URL:
https://issues.jboss.org/browse/JBIDE-11264
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 3.3.0.Beta1
Reporter: Lucia Jelinkova
Assignee: Andre Dietisheim
Priority: Critical
Fix For: 3.3.0.Beta2
Attachments: import.ogv, untitled.mp4
When I have an existing OpenShift application with name different that the artifact id in
pom file and I want to import it into Eclipse workspace, I get different Eclipse project
names depending on the chosen location of the newly created workspace file.
# when selected default value (/home/xxx/git) the project's name is the one from pom
file
# when selected the workspace location the project's name is the OpenShift
application name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira