[
http://jira.codehaus.org/browse/MECLIPSE-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_115102
]
Arnaud Heritier commented on MECLIPSE-334:
------------------------------------------
Can't it be dangerous to create project dependencies to projects that don't
(yet) exist ?
> Add a rule that determined artifacts will be always recognized as reactor
> projects
> ----------------------------------------------------------------------------------
>
> Key: MECLIPSE-334
> URL: http://jira.codehaus.org/browse/MECLIPSE-334
> Project: Maven 2.x Eclipse Plugin
> Issue Type: New Feature
> Affects Versions: 2.4
> Reporter: Martin Zeltner
> Attachments: patch_maven-eclipse-plugin-r587020.patch
>
> Original Estimate: 10 minutes
> Remaining Estimate: 10 minutes
>
> I've implemented a feature that determined artifacts will be always
> recognized as reactor projects, doesn't matter where the "mvn
> eclipse:eclipse" is executed. The idea is to set a list of groupId prefixes.
> Example:
> [code]
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-eclipse-plugin</artifactId>
> <configuration>
> <reactorProjectGroupIdPrefixes>
> ch.elca.,
> org.sp,
> net.sf
> </reactorProjectGroupIdPrefixes>
> </configuration>
> </plugin>
> [/code]
> All artifacts where the groupId starts with "ch.elca.", "org.sp" or "net.sf"
> will be handled as reactor projects.
> Cheers,
> Martin
--
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
