[
https://issues.jboss.org/browse/JBIDE-11264?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-11264:
------------------------------------------
From an outside (to maven import) perspective I see no difference in
both use cases in our code. The differing result therefore must be caused by the maven
import component. This maven import is not in our control, the best we can do for now is
to warn about/disallow locations in the workspace. This would match good practices which
suggest stronlgy to not use locations in the workspace (this is true for all kind of
non-project artifacts: for target platforms, svn repos, etc.).
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