Actually, I am somewhat reserved against moving to higher Java versions without need.
There are a lot of applications dependent upon xerces which are already out and running that depend upon certain Java versions and cannot be upgraded. Therefore such a switch should only be made if there is cause that justifies this (as there was in November[1]). Developers usually prefer newer Versions so they can take advantage of new flashy features however operation usually prefers to stick to older versions as long as possible to reduce the impact a version change has upon up and running applications and services. Ludger [1] http://issues.apache.org/jira/browse/XERCESJ-1297 > -----Original Message----- > From: Mukul Gandhi [mailto:[email protected]] > Sent: Friday, May 08, 2009 2:03 PM > To: [email protected] > Subject: Re: Xerces on Java 5 > > On Thu, May 7, 2009 at 1:03 PM, Hiranya Jayathilaka > <[email protected]> wrote: > > +1 to supporting Java 6. But first we need to decide on a migration > strategy > > which does not affect the Xerces users on Java 1.3. > > One possible strategy to migrate to JRE 1.5 could be, that we can use > a tool like Retroweaver (ref, http://retroweaver.sourceforge.net/). > > We can develop future code of Xerces-J using Java 1.5 constructs, and > use the Retroweaver utility to transform the 'Xerces JAR' developed > using JDK 1.5 to another JAR, which can run on JRE 1.3 or 1.4. > > We can ship a JRE 1.5 JAR and say other JARs each for JRE 1.3 and JRE > 1.4. > > We can probably do a small pilot to test the feasibility. I have > learnt, that Retroweaver is a reliable utility, and is used in number > of open source projects, where binary compatibility with earlier JRE > versions is required. > > Unfortunately, Retroweaver currently doesn't support JDK 1.6 to > 1.4/1.3 conversion. We need to use JDK 1.5. > > > -- > Regards, > Mukul Gandhi > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > -- > This message was scanned by ESVA and is believed to be clean. > Click here to report this message as spam. > http://mailfilter.nc-sb.de/cgi-bin/learn-msg.cgi?id=2D47D27F21.665C8 >
