Retroweaver [1] is probably a more current tool. Sun's is from 2001, I think. But still, if we change to 1.5 within a year anyway, it's probably not worth going through that learning-curve. You still have to make sure you don't use any new features from the 1.5 class-library. And there are a few nice things to be found there.
[1] http://retroweaver.sourceforge.net/ Jeremias Maerki On 19.10.2007 14:56:18 Max Berger wrote: > Dear XMLGraphics Dev, > > another option (although the acutal usability will have to be tested) is > to require the generics/enum/autoboxing precompiler, which is available > at: > > http://java.sun.com/developer/earlyAccess/adding_generics/ > > and produces 1.3 and 1.4 compatible class files. > > Max > > Am Freitag, den 19.10.2007, 11:08 +0100 schrieb Vincent Hennebert: > > Hi, > > > > Andreas L Delmelle wrote: > > > On Oct 17, 2007, at 10:16, Jeremias Maerki wrote: > > > > > >> No reactions so far. Interesting. Anyway, based on the user poll, my > > >> opinion is to go for Java 1.4 for the moment and reevaluate Java 1.5 > > >> next summer. I mean I'd love to use generics and java.util.concurrent > > >> but I think it is just a bit too soon to drop 1.4. > > >> > > >> Any objections to that course of action? Should we have a majority > > >> decision on whether 1.4 or 1.5 should be the new minimal Java level? > > > > > > Not as far as I'm concerned. +1 for staying with 1.4 for the time being. > > > > > > Chris is right. We don't really /need/ 1.5 to implement new features. It > > > would be more a convenience than a necessity, so has very low priority > > > IMO. > > > Should anyone feel compelled to use 1.5, he could always integrate it > > > much in the same way the 1.3-1.4 gap has been dealt with (separate build > > > targets to be able to build on both versions without too much hassle). > > > > AFAIK you can’t produce 1.4-compatible bytecode if the source code has > > the new features introduced in 1.5 (annotations, generics, type-safe > > enums). So that would be nearly useless to maintain separate branches, > > as the 1.5 one would only allow to use classes from the standard library > > which aren’t available in 1.4. And we can actually live without those > > classes. > > > > Granted, 1.5 features are more a convenience than a necessity, but they > > are so much more convenient... > > > > Ok, I’m repeating myself, shutting up now. > > Vincent --------------------------------------------------------------------- Apache XML Graphics Project URL: http://xmlgraphics.apache.org/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
