-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > > Off topic. > > Actually I believe this isn't true anymore. > > See http://jira.codehaus.org/browse/MECLIPSE-344 > "all dependent artefacts that are available in your eclipse-workspace > will be attached as project references even if they are not in the > reactor." > It was fixed in 2.5 > > Can you try it on your project structure and confirm? > > I know it works for me. > > I have this structure > > common projects > - module cA > ... > - module cZ > > My project > - module pA > ... > - module pZ > (where some of these projects depend upon projects from commons) > > mvn eclipse:eclipse will make sure my module pA references the eclipse > project for module cA (and not the jar of cA in the repo)
Thanks for the hint! But only works if eclipse-plugin knows where my workspace is. The location may be different for each developer so I can NOT truly automate. Anyhow I will start using this. At least better solution than what I had before. Thanks Jörg -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkoNxrQACgkQmPuec2Dcv/8VrQCdGu/eWpZnifkPYdW/u+6RqsKx +eMAnRv5/EHXo0895onKGsmExxxtoC70 =gj/Z -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
