On Wed, Mar 31, 2010 at 12:53 PM, Gabriele Columbro <[email protected]> wrote: > On Mar 31, 2010, at 11:06 AM, Klevenz, Stephan wrote: >> I had quite a lot of trouble using m2eclipse and just skipped it. Since I'm >> using >> mvn eclipse:eclipse >> everything is fine with Eclipse integration of Maven. This is really simple. > > So the good thing why I use m2eclipse is to be able to manage multiple > modules as a single project so that I can have full control over it (e.g. for > bulk SVN changes) and for other dependency analysis tools. > IIRC when you mvn eclipse:eclipse a multimodule project you end up with a > .classpath for each of submodules and I want to avoid that. > Are you able using mvn eclipse:eclipse to have a single project and pull up > all submodules source folders and dependencies like m2eclipse does?
Yes as long as you start the mvn eclipse:eclipse from the toplevel containing directory. Then all bundles referencing each other are seen as workspace source dependencies, not M2_REPO ones. When needed I have also a shell script that does sed surgery on the .classpath to turn M2_REPO references to some projects to workspace source dependencies. > Actually the issue is definitely related to Java5 / Java6 settings for my > project as I noticed an old reference to JVM5 system library in the Eclipse > project: unluckily though, when changing that to JVM 6 system library, while > the original AtuhHandler problem disappear (still sorting out other local > issue though). Good that it's fixed for you. Florent -- Florent Guillaume, Director of R&D, Nuxeo Open Source, Java EE based, Enterprise Content Management (ECM) http://www.nuxeo.com http://www.nuxeo.org +33 1 40 33 79 87
