[
http://jira.codehaus.org/browse/MECLIPSE-473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=143723#action_143723
]
Moshe Bergman commented on MECLIPSE-473:
----------------------------------------
Just to clarify, this would result in the project names:
Category.<artifactId>
For example, if I have artifactId "Client" in: 1) com.aaa.bbb.ccc.Category1 and
2) com.aaa.bbb.ccc.Category2,
The result would be:
1) Category1.Client
2) Category2.Client
> Allow removing common part of groupId for project name
> ------------------------------------------------------
>
> Key: MECLIPSE-473
> URL: http://jira.codehaus.org/browse/MECLIPSE-473
> Project: Maven 2.x Eclipse Plugin
> Issue Type: New Feature
> Components: Core : Multi-projects
> Affects Versions: 2.5.1
> Reporter: Moshe Bergman
>
> Same problem as previous JIRA's. Having multiple projects with the same
> artifactId in different groupId's.
> However, using addGroupNameToProjectName creates a long project name, since
> our projects have this format for grouId: com.aaa.bbb.ccc.Category.
> Would it be possible to add excludeGroupName option. So I can specify
> "com.aaa.bbb.ccc" as excluded?
--
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
