[jbosstools-issues] [JBoss JIRA] (JBIDE-11264) Wrong workspace project name when the OpenShift app name != artifact id in pom file and the project location is within the workspace

[Andre Dietisheim (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-11264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676305#comment-12676305 ] 

Andre Dietisheim edited comment on JBIDE-11264 at 3/13/12 5:06 AM:
-------------------------------------------------------------------

ok, good catch. I tried to reproduce it manually and was perfectly able to:


1.) ASSERT: have a git repo that holds a maven project in a single subdir - no nested subdirs (ex. <git repo>/*a-project*/.git, pom.xml etc.). Make sure the project has NO .project.
2.) EXEC: change the artifact id in the pom.xml (ex. *a-project-changed*)
3.) EXEC; clone the git repo into your workspace (ex. <your home>/runtime-workspace/*a-project*)
4.) EXEC: File->Import->Maven->Existing Maven Projects
5.) EXEC: The maven import will detect your project and display /*a-project*/pom.xml. Pick it and finish the wizard.

Results:
The maven import will import a new project to your workspace, the project will hold the name of the directory it is in, not the artifact-id (ex. *a-project* and *NOT a-project-changed*)
                
      was (Author: adietish):
    ok, good catch. I tried to reproduce it manually and was perfectly able to:


1.) ASSERT: have a git repo that holds a maven project in a single subdir - no nested subdirs (ex. <git repo>/*a-project*/.git, pom.xml etc.)
2.) EXEC: change the artifact id in the pom.xml (ex. *a-project-changed*)
3.) EXEC; clone the git repo into your workspace (ex. <your home>/runtime-workspace/*a-project*)
4.) EXEC: File->Import->Maven->Existing Maven Projects
5.) EXEC: The maven import will detect your project and display /*a-project*/pom.xml. Pick it and finish the wizard.

Results:
The maven import will import a new project to your workspace, the project will hold the name of the directory it is in, not the artifact-id (ex. *a-project* and *NOT a-project-changed*)
                  
> 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