It has actually been much easier to package it as this "monolithic" aspect library over the past few years. If there is a bug or feature addition in any of the aspects in the library, I can easily patch any version of JBoss. It would actually be more "monolithic" if the code was part of Branch_4_0 as I would not be able to do a new release of the aspect library (and EJB 3.0 for instance) without a complete rev of the entire application server. This is quite unacceptable to most users.
So, in summary, although I think it might be asthetically appropriate, I don't see how this change you suggest will make anybody's life easier. It sure will make the EJB3/AOP team's life much harder to do new releases. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3874331#3874331 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3874331 ------------------------------------------------------- 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 JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
