[
http://jira.codehaus.org/browse/MECLIPSE-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_115184
]
Martin Zeltner commented on MECLIPSE-334:
-----------------------------------------
Example:
Directory structure:
mymodules/
a/
b/
c/
* a, b and c are subdirs of dir mymodules
* mymodules contains a pom.xml that has a, b and c as modules
* a, b and c contain also a pom.xml
* c depends on b depends on a
I'd like to have a, b and c in one workspace:
* cd mymodules
* mvn eclipse:eclipse
a, b and c are now in the workspace. I change a dependency in pom.xml c so I
have to execute the following:
* cd mymodules/c
* mvn eclipse:clean eclipse:eclipse
I go back to my workspace and refresh project c (F5). Without my new feature
the project c in Eclipse has now NO MORE dependent on a and b (direct link to
local repo). To solve this issue with the current eclipse plugin I have to
recreate the Eclipse project for a, b and c like at the beginning.
* cd mymodules
* mvn eclipse:clean eclipse:eclipse
> 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
