[
http://jira.codehaus.org/browse/MECLIPSE-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_115171
]
Martin Zeltner commented on MECLIPSE-334:
-----------------------------------------
I don't understand what's dangerous. First this feature is switched off by
default (property not set). Second if you miss to import an eclipse project
into the workspace you will have the same "danger" as currently. Could you
please explain me what "danger" do you see with my extension that we don't have
already?
> 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
