You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "David Rice (JIRA)" <ji...@codehaus.org> on 2006/01/04 17:22:10 UTC

[jira] Updated: (MNG-1920) Allow custom project name for eclipse projects

     [ http://jira.codehaus.org/browse/MNG-1920?page=all ]

David Rice updated MNG-1920:
----------------------------

    Attachment: MNG-1920-maven-eclipse-plugin.patch

> Allow custom project name for eclipse projects
> ----------------------------------------------
>
>          Key: MNG-1920
>          URL: http://jira.codehaus.org/browse/MNG-1920
>      Project: Maven 2
>         Type: New Feature

>     Versions: 2.0.1
>     Reporter: David Rice
>  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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org