On Tue, 16 Oct 2012 07:04:56 AM Michael Vehrs wrote: > However, if you have any statistics showing that the market share of > Java 1.5 has declined below 10% or so, then I see no reason why we > should not move to 1.6. That would certainly provide some benefits, such > as better font support and good-bye woodstox.
That seems like a fair test. Googling around comes up with http://www.statowl.com/java.php who put Java <=1.5 at about 4%, 1.6 at 57%, 1.7 at 9%, with 30% unknown. Not very convincing given the last category, but I would not be that surprised if the real value is close to the 10% mark. What concerns me more is that 1.5 is deprecated and thus not getting (rather necessary) security updates. Therefore, my suggestion is that we drop the 1.5 compatibility requirement after the 0.1.6 release. Cheers, Mike Pope
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________ Freecol-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freecol-developers
