Sorry, my answer were cut by forum parser. It is without quote: I think the same. Earlier I have worked on simple project with 20 maven 1.x modules. Editing with eclipse was horrible. maven 1.x even doesn't resolve dependent projects and only leave dependencies to maven repository No I'm working on big project with 150 maven 2 modules ! Fortunately maven 2 eclipse plugin better resolve project despondencies but sucks with classpath ordering and editing 150 .classpath is unacceptable without some templating system (not necessary maven ;)). I know that 150 modules cause system much more modular ;) and it is need in some cases but it cant block developing and reffactoring. Correct configured IDE is essential and need well-thought-out build system. Without this, modularizies is over marketed IMHO and very slows developing. My brother works on 3 modules project in Netbeans, not maven, Yes, one centrized IDE but deploying cycle occupy only 5 seconds with all sources available ! Short deploing cycle is critical to developing IMHO. I'm sometimes frustrated with modularization without proper configruation. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4167426#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...