There does need to be some sanity check the developer or cruise control can perform before the final release, to make sure the java5 feature is supported by the retroweave.
With the new build, adding a retroweave target should be enough. This would then work its way through the jars going into the release and make sure they have weaved and validated for supported features. Getting cruise control to retroweave and run the testsuite against jdk1.4 should catch errors where developers aren't testing this scenario themselves (most of them). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866705#3866705 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866705 ------------------------------------------------------- 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
