maven eclipse:eclipse plugin: multiproject parent of the parent modules generated incorrectly

[Vytautas Civilis <ci...@idega.com>]

Hello.

Problem is with the maven eclipse:eclipse plugin.

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.

Any help is appreciated. Trying to get rid of those m2eclipse plugins
(which are horribly slow).

cvl

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org