0 At this point after talking with some clients, I think it is still a problem to widely switch to 1.5 at this point. Many big customers are running WebSphere 6.0 which is Java 1.4. We could exclude ourselves from these users, so we need to be carefull. I would vote +1 for a default build in java 1.5 as long as we don't change core libraries to only 1.5 compatible library but only new non critical features that are only 1.5. Which means we should still be able to compile a limited version of XWiki in 1.4 by excluding these additionals non compatible features. This also means which should not include any 1.5 language features in our core code Ludovic Vincent Massol a écrit :
Hi,
I think it's time to officially decide if we want to standardize on 1.5. Some reasons we may want to do this:
* JDK 1.4 is old. 1.5 is mainstream. 1.6 is about to be released. * Most libraries have now switched to 1.5 and it's going to be real hard to stay on 1.4 if we want to get bug fixes/new features from the libraries we use * Radu needs to use some google jars for his GSOC and they seem to require JDK 1.5 * We already require 1.5 I believe (although it's a light dependency) and have been requiring 1.5 for now several months (> 5 months) and we haven't heard complaints from users about this
The vote is about officially dropping support for 1.4 and standardizing on 1.5 (and thus allowing us to use the new features of the language too like generics, annotations, etc).
Here's my +1
Please cast your votes.
Thanks -Vincent
------------------------------------------------------------------------
-- You receive this message as a subscriber of the [email protected] mailing list. To unsubscribe: mailto:[email protected] For general help: mailto:[email protected]?subject=help ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
-- Ludovic Dubost Blog: http://www.ludovic.org/blog/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost AIM: nvludo Yahoo: ludovic