I'd like to alleviate the concern (at least for Xerces-J) there seems to be about what JVMs and versions will be supported.
Back in January the Xerces-J committers voted [1] to discontinue support for JDK 1.1 after the Xerces 2.6.1 release. That is something we had held off doing for a long time but we finally decided to move up to JDK 1.2. Given how old JDK 1.2 is I don't consider that to be a big step up, though I do acknowledge that users on some platforms are still stuck on JDK 1.1. We have not discussed moving up to a higher JDK version nor do I feel such a discussion will happen in the near future. Unless there's some compelling reason for a change in JDK version, Xerces 2.7.0 will require JDK 1.2 or higher. If the RI doesn't compile or run on JDK 1.2, then we'll look into it. My gut feeling is that this won't be a problem. Thanks. Shane Curcuru <[EMAIL PROTECTED]> wrote on 10/12/2004 11:53:18 AM: > A couple of comments: > - Please cc: [EMAIL PROTECTED], since xml-commons is the > actual repository that holds the JAXP code. > > - Yay! Great progress all, both Xerces/Xalan folks for coordinating, > and Sun folks for getting the process unstuck. 8-) > > - Both Elliotte's and Clay's questions below are important. If someone > familiar with the code could comment on: For either the main trunk, or > a temporary working branch for integration: > > -- What JVM's will this code compile on? Version/Vendors? > > -- What JVM's will this code run on? Version/Vendors? > > We need to *clearly* document which versions this stuff works on, and > should conditionally compile or something if it won't compile on at > least 1.3 (since we still have a lot of older JDK version users here). > > My knee-jerk reaction is also to hope that it will compile & run on > both recent Sun and IBM JVMs at least before we put this on the main > trunk: we should really try to be JVM-vendor agnostic. (anyone still > working on kaffe? 8-) [1] http://issues.apache.org/eyebrowse/[EMAIL PROTECTED]&msgNo=3461 Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: [EMAIL PROTECTED] E-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
