In theory, a 10.2 level Derby release would not need/have to be recompiled if the JARs are available for download - hence we are saying that we will still support a 10.2 release running with jdk/jre 1.3, right? 1.3 is kinda ancient as we know...
+1 On 8/10/05, Lance J. Andersen <[EMAIL PROTECTED]> wrote: > +1 > > Rick Hillegas wrote: > > > +1 > > > > Rick Hillegas wrote: > > > >> No-one on the user list has objected to the proposed sunsetting > >> policy for jdk 1.3. Therefore I'm cautiously hopeful that we can > >> move forward with a vote. Let's wrap up the voting by Friday evening > >> (12 August, 2005). > >> > >> Thanks, > >> -Rick > >> > >>> Please vote on the following proposed policy for Derby's supported > >>> platforms. Mostly, this proposal merely restates the current policy. > >>> Changes are flagged. > >>> > >>> o 10.2 will be the LAST Derby release which runs on jdk 1.3 and > >>> supports JDBC 2.0. > >>> THIS IS A CHANGE FROM CURRENT POLICY. > >>> > >>> o 10.2 will run on the following platforms: > >>> > >>> - J2ME/CDC/Foundation 1.0 (exposing the JDBC subset in JSR 169) > >>> - 1.3.x (exposing JDBC 2.0) > >>> - 1.4.x and 1.5.x (exposing JDBC 3.0) > >>> - 1.6 beta (exposing JDBC 4.0) THIS IS A CHANGE FROM CURRENT POLICY. > >>> > >>> o To build 10.2, you MUST have the 1.3 and 1.4 sdks. > >>> > >>> o The 10.2 build will expose an optional target for building JDBC 4.0 > >>> support. To use this target, you must have a 1.6 sdk. THIS IS A > >>> CHANGE. > >>> > >>> > >>> > >> > >> > > > > >
