[ http://jira.codehaus.org/browse/MECLIPSE-119?page=comments#action_78208 ]
Andrea Aime commented on MECLIPSE-119:
--------------------------------------
This inability to customize the project is byting us (Geotools/Geoserver
projects) as well... we do have a "main" module in both projects, and at the
same time maven works better if you have directory name=module name (see scm
tags handling).... even having the ability to just write to the "project"
property would be nice, it would allow for a customisation like:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-eclipse-plugin</artifactId>
<configuration>
<project>gt2-${project}</project>
</configuration>
</plugin>
> 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
