maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kenney Westerhof (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MECLIPSE-119) Allow custom project name for eclipse projects
Date Sat, 07 Oct 2006 02:14:27 GMT
    [ http://jira.codehaus.org/browse/MECLIPSE-119?page=comments#action_76879 ] 
            
Kenney Westerhof commented on MECLIPSE-119:
-------------------------------------------

I prefer a switch like 'eclipse.addVersionToProjectNames'. 

The -Declipse.projectname=LITERAL_STRING is dangerous and won't work in a reactor build.

> 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
>         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