> For Fedora development, if we moved to Java6-only compatibility, we could: > - Get rid of the JDBC version code-rewriting hack during the build > - Start using certain annotations and core library methods/classes > that were newly introduced since 1.6 > - Remove Java5 from future test plans (shortening the test cycle for now...)
I think this move makes sense. Not only does it provide the opportunity for an easier/cleaner build and release process, but it provides compatibility with some contemporary third-party library releases that require 1.6. "Go forward, not backward. Upward, not forward. And always twirling, twirling..." -Aaron ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Fedora-commons-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fedora-commons-developers
