Well, when you are a framework, you tend to try and stick to "lowest possible denominator" to ensure its usefulness in as many places as possible.
Minor things, like you mention, doesn't seem to validate moving up to 1.6 just yet, IMVHO. On Wed, Jun 23, 2010 at 10:01 PM, Stanislav Muhametsin <[email protected]> wrote: > Quoting Niclas Hedhman <[email protected]>: > >> Hmmmm.... That is actually a bug in that case. Everything should be >> built by 1.5 compiler. >> > > Speaking of that, any chance of Qi4j project moving to 1.6 compiler? The JDK > 1.6 provides the class java.util.ServiceLoader, equivalent implementation of > which is in org.qi4j.bootstrap.internal.ServiceLoader . Additionally, the > @Override annotation works on class methods implementing interface methods. > Not to mention numerous other improvements and additions that 1.6 introduces > over 1.5. > > Or is 1.6 a problem for some OS or is there some other reason why 1.5 is > specifically preferred over 1.6 ? > > > > _______________________________________________ > qi4j-dev mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/qi4j-dev > -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java I live here; http://tinyurl.com/2qq9er I work here; http://tinyurl.com/2ymelc I relax here; http://tinyurl.com/2cgsug _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
