maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Casey (JIRA)" <j...@codehaus.org>
Subject [jira] Moved: (MECLIPSE-119) Allow custom project name for eclipse projects
Date Thu, 22 Jun 2006 17:22:40 GMT
     [ http://jira.codehaus.org/browse/MECLIPSE-119?page=all ]

John Casey moved MNG-1920 to MECLIPSE-119:
------------------------------------------

       Version:     (was: 2.0.1)
                2.2
    Complexity:   (was: Intermediate)
           Key: MECLIPSE-119  (was: MNG-1920)
       Project: Maven 2.x Eclipse Plugin  (was: Maven 2)

> Allow custom project name for eclipse projects
> ----------------------------------------------
>
>          Key: MECLIPSE-119
>          URL: http://jira.codehaus.org/browse/MECLIPSE-119
>      Project: Maven 2.x Eclipse Plugin
>         Type: New Feature

>     Versions: 2.2
>     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


Mime
View raw message