Ok with me. But remember we want to get to the stage ASAP where JBoss Cache and JBoss AOP can be true standalone projects.
This obviously means we need to implement the repository to do what you are proposing, but we also need to test the new build against jboss-head so we can then backport it to jboss3/4 Only when this is all done will these standalone projects be able to easily develop their code/branches and target different releases of JBoss and QA/Labs be able to manage the process. The only option for these standalone projects at the moment is to deliver binaries to the different JBoss releases hoping for the best that everything hangs together with the thirdparty jar versions and other dependencies. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3865746#3865746 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3865746 ------------------------------------------------------- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
