[jira] Closed: (MECLIPSE-119) Allow custom project name for eclipse projects

["Carlos Sanchez (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MECLIPSE-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carlos Sanchez closed MECLIPSE-119.
-----------------------------------

      Assignee: Carlos Sanchez
    Resolution: Duplicate

> Allow custom project name for eclipse projects
> ----------------------------------------------
>
>                 Key: MECLIPSE-119
>                 URL: http://jira.codehaus.org/browse/MECLIPSE-119
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: New Feature
>    Affects Versions: 2.2
>            Reporter: David Rice
>         Assigned To: Carlos Sanchez
>         Attachments: MNG-1920-maven-eclipse-plugin.patch
>
>
> If you download 2 versions of the same artifact, or 2 artifacts with the same artifactId then when you create eclipse the projects you have to load them into different workspaces because the eclipse project name is the same (ie. based on artifactId).  I added a parameter eclipse.projectName to allow you to specify an alternate name to artifactId to get around this problem.
> Example uses:
> -Declipse.projectName='${project.artifactId}:${project.version}'
> -Declipse.projectName='${project.groupId}:${project.artifactId}:${project.version}'
> -Declipse.projectName=my-different-project-name

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira