[
http://jira.codehaus.org/browse/MECLIPSE-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=217307#action_217307
]
Johan Walles commented on MECLIPSE-483:
---------------------------------------
I was just hit by this; it is still borken in 2.9-SNAPSHOT.
> eclipse:eclipse fails to generate references to eclipse workspace projects on
> multiparent module structure
> ----------------------------------------------------------------------------------------------------------
>
> Key: MECLIPSE-483
> URL: http://jira.codehaus.org/browse/MECLIPSE-483
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Reporter: Vytautas Civilis
>
> To make it simpler, I have following modules structure:
> Parent A -> extends -> Parent B
> Parent B defines modules: B.m1 and B.m2
> Parent A defines modules: A.m3 and A.m4
> Using flat layout, if that matters, so B, m1, m2, A, m3, m4 are in the
> same workspace folder, to make things easier.
> Now, when generating .classpath for modules in B, the .classpath files
> are correct -> module m1 reference _eclipse project_ of the m2 (if it does
> depend of course).
> Contrary, generated .classpath for A is incorrect. If the module A.m3
> depends on B.m1, then .classpath will contain reference to the B.m1 _jar_,
> but _not_ eclipse project. That's because module B.m1 is not explicitly
> specified in A modules (which it shouldn't). In other words, mvn
> eclipse:eclipse fails to look up deeper than one parent.
> I suggest eclipse:eclipse should lookup all the way up parents tree for
> defined modules, that exist in the eclipse workspace.
> cvl
--
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
