[
https://issues.jboss.org/browse/JBIDE-11264?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-11264:
---------------------------------------------
Nope, I do not agree :)
Have you verified that a basic maven import when done outside our wizard/code behaves the
same ? i.e. import a project within a workspace manually repeats the same problem ?
if it works fine manually then something is wrong in our import code and we should fix it.
if it does not work and thus it is an m2eclipse problem then:
A) fbricon is a committer on m2eclipse so we do influence this.
B) if A can't be done in time then adding a warning or maybe even error validation
about output being inside workspace would be fitting since i'm sure others will
attempt this.
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: Max Rydahl Andersen
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