m2eclipse supports both styles of dependency resolution - 1) resolving using normal maven dependency resolution (usually, the prebuilt jar in the .m2 local repository), or 2) from the current workspace (allowing you to "pick up" changes there, even if the other project(s) weren't built/installed.
This is described in the m2eclipse book, here: http://www.sonatype.com/books/m2eclipse-book/reference/dependencies.html#dependencies-sect-resolving-dependencies -Marshall Schor On 10/2/2010 7:22 AM, Antonio Petrelli wrote: > 2010/10/2 Iron Eagle <[email protected]>: >> Some times, I use the command line (there its no problem). But most time, I >> use eclipse. I've searched for a tutorial for that problem, but the result >> doesn't really satisfy me. > If you use m2eclipse and you checkout the entire main pom project as > Maven project, the project created for module B will have a reference > to the project for module A. > > Antonio > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
