You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Martin Zeltner (JIRA)" <ji...@codehaus.org> on 2007/12/10 09:11:57 UTC

[jira] Commented: (MECLIPSE-334) Add a rule that determined artifacts will be always recognized as reactor projects

    [ http://jira.codehaus.org/browse/MECLIPSE-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116337 ] 

Martin Zeltner commented on MECLIPSE-334:
-----------------------------------------

After the discussion with Richie I'm convinced now that the MECLIPSE-344 covers my needs too. But dealing with files in the workspace folder looks to me a bit dangerous because they seem to be not so stable in their format as the .project and .classpath.

> 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