[jbosstools-issues] [JBoss JIRA] (JBIDE-11264) When project is inside eclipse workspace Maven import gets the application name wrong
[
https://issues.jboss.org/browse/JBIDE-11264?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen updated JBIDE-11264:
----------------------------------------
Summary: When project is inside eclipse workspace Maven import gets the
application name wrong (was: Wrong workspace project name when the OpenShift app name !=
artifact id in pom file and the project location is within the workspace)
Fix Version/s: 3.3.x
(was: 3.3.0.Beta3)
Priority: Major (was: Critical)
Assignee: Fred Bricon (was: Max Rydahl Andersen)
Component/s: UpStream
Not for beta3 since the issue is upstream.
Not critical since it only happens if your project is within the workspace which is bad
practice anyway :)
Moved to 3.3.x for investigation by Fred for fix in m2e core.
When project is inside eclipse workspace Maven import gets the
application name wrong
-------------------------------------------------------------------------------------
Key: JBIDE-11264
URL: https://issues.jboss.org/browse/JBIDE-11264
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift, UpStream
Affects Versions: 3.3.0.Beta1
Reporter: Lucia Jelinkova
Assignee: Fred Bricon
Fix For: 3.3.x
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