I personally use a completely different approach when the parent + child modules are really a self-contained project (and you always want to work on all of them).
* I open the parent project in Eclipse. All the child modules show up as sub-folders * I add each main and test source and resource folder to Eclipse build path as source folders and customize their target directories appropriately. I do this for each child module too. * I use the Maven2 eclipse plugin to automatically add all the dependencies to the classpath. * I commit to version control the .project and .classpath files I end up with a single classpath in Eclipse across all sub-modules. When I add new dependencies to pom.xml, the Maven2 plugin updates my classpath. Tim Alexander Sack-3 wrote: > > http://maven.apache.org/plugins/maven-eclipse-plugin/reactor.html > > -aps > > On 1/26/07, Marco Mistroni <[EMAIL PROTECTED]> wrote: >> >> hi all, >> i still havent' managed to use maven2 with eclipse where i have a >> parent >> project and few children project >> >> has anyone managed to have that setup working correctly in eclipse? >> >> any hints on how to make it work will be greatly appreciated >> >> regards >> marco >> >> > > > -- > "What lies behind us and what lies in front of us is of little concern to > what lies within us." -Ralph Waldo Emerson > > -- View this message in context: http://www.nabble.com/maven2%2C-eclipse-and-hierarchical-layout-tf3123649s177.html#a8668829 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
