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

["Karl Heinz Marbaise (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MECLIPSE-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karl Heinz Marbaise updated MECLIPSE-334:
-----------------------------------------
    Comment: was deleted

(was: That's really cool. I would be interested in seeing more graphs of different information you pull from these logs.
http://zngamehack.com)

> Add a rule that determined artifacts will be always recognized as reactor projects
> ----------------------------------------------------------------------------------
>
>                 Key: MECLIPSE-334
>                 URL: https://issues.apache.org/jira/browse/MECLIPSE-334
>             Project: Maven Eclipse Plugin (RETIRED)
>          Issue Type: New Feature
>    Affects Versions: 2.4
>            Reporter: Martin Zeltner
>            Assignee: Arnaud HERITIER
>         Attachments: patch_maven-eclipse-plugin-r587020.patch
>
>   Original Estimate: 10m
>  Remaining Estimate: 10m
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)