Hi guys, If I may, what's not supported is the following: | /root | pom.xml | /module1 | pom.xml | /module2 | pom.xml | This is the standard Maven 2 layout, but if you run mvn eclipse:eclipse at the root, it will generate the following which is not supported by eclipse: | /root | .project | .classpath | pom.xml | /module1 | .project | .classpath | pom.xml | /module2 | .project | .classpath | pom.xml | That's the nested kind of projects that eclipse doesn't support. Whereas, the following alternative (known as "flat" in the M2 doc) is a safe layout: | /root | /root | pom.xml | /module1 | pom.xml | /module2 | pom.xml | Because if you run mvn eclipse:eclipse at the root, it will generate the following which is supported by eclipse: | /root | /root | .project | .classpath | pom.xml | /module1 | .project | .classpath | pom.xml | /module2 | .project | .classpath | pom.xml | For more information, here is the Maven 2 documentation: http://maven.apache.org/guides/mini/guide-ide-eclipse.html By the way, I'm really glad that you guys are looking into migrating the JBoss build system to Maven 2. As a long time Maven (1 and 2) user and a JBossAS afficionados, it has always been tricky to use JBoss libraries from a Maven 2 project (and before Maven 1). Such a move will make things a lot easier ! Is there a road map regarding that migration plan ? Cheers View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3958076#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...