[
http://jira.codehaus.org/browse/MECLIPSE-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carlos Sanchez reopened MECLIPSE-251:
-------------------------------------
There are problem with the syntax used, it doesn't work in the reactor as the
variables (${groupId}, ${artifactId}) are injected by maven
> Allows prefixing of eclipse project name
> ----------------------------------------
>
> Key: MECLIPSE-251
> URL: http://jira.codehaus.org/browse/MECLIPSE-251
> Project: Maven 2.x Eclipse Plugin
> Issue Type: New Feature
> Components: multiproject
> Affects Versions: 2.4
> Reporter: Martin Desruisseaux
> Assignee: Carlos Sanchez
> Fix For: 2.4
>
> Attachments: 20070509-maven-eclipse-plugin.patch
>
>
> This issue is related to MECLIPSE-44, MECLIPSE-119 and MECLIPSE-161. They
> were closed as fixed by MECLIPSE-189, but the later doesn't adress fully our
> issue (or works only if we are lucky).
> We have two Maven projects (namely _Geotools_ and _Geoserver_) made of many
> modules. Some Geoserver modules may (by accident) have the same name than
> Geotools modules. For example both Geotools and Geoserver have a module named
> "_main_". We need to import those two projects in Eclipse, because they are
> closely related and share the same pool of developpers. Before MECLIPSE-189,
> it was not possible with those names, because of module name clash like
> "_main_". Since MECLIPSE-189, it is possible if we are lucky enough to have
> different Geotools and Geoserver version numbers.
> We would like a way to prefix every Eclipse module names. For example we
> would like a way to add {{"gt-"}} in front of every Geotools modules imported
> in Eclipse. I realize that the common practice in Maven projects seems to be
> long module names (for example "{{maven-eclipse-plugin}}"), but such practice
> seems quite redundant with group name. We would like to keep module names
> that match SVN directory names or Maven report directory names (otherwise we
> often get broken links in generated HTML pages), and we would like to keep
> the path names simple and intelligible (long module names don't bring much
> compared to full path names, which should already be unique).
> The ability to add some prefix before Eclipse project names would help. If
> this is not possible, something like {{addGroupNameToProjectName}} property
> (similar to {{addVersionToProjectName}} defined in MECLIPSE-189) could be a
> fallback.
--
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
