It seems like many of these issues are symptomatic of the application server project hosting the code of so many super-subprojects like aop and the microcontainer. Are these going to be split into their own projects? IE, can aop become a thirdparty jar for the application server?
I have put together some ideas on how the build system might deal with such an organization. http://www.jboss.org/wiki/Wiki.jsp?page=BuildDependencyManagement It also addresses management of thirdparty libraries in a more scalable manner. As an aside, by providing declarative dependencies, it would be possible to do things like automatically generate eclipse .classpath files automatically. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3859536#3859536 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3859536 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
