Michael Segel wrote: > >> -----Original Message----- >> From: Geir Magnusson Jr [mailto:[EMAIL PROTECTED] >> Sent: Tuesday, September 12, 2006 5:38 AM >> To: [email protected] >> Subject: 10.2 licensing issue... >> >> I read Rick's note on the 10.2 licensing issue in an archive because of >> strange move to the user list, so sorry for the weird quoting : >> >> He said : >> >> "I must report today that the restrictions imposed by the beta JDK >> license have not been lifted. >> >> As you know, the JDK 6 beta license requires a disclaimer that bars the >> use of the code for any productive use.... >> >> snip >> >> ...For this reason, we, the Derby community must change our >> plan to ship imminently an official release of Derby that includes JDBC4." >> > > >> Let me start with a question : >> >> Why? Is this all about having a set of API jars to compile against, or >> is it something more? >> >> >> geir > > Something more. > > The trouble is that JDK 6 isn't ready for primetime and from the discussion, > 10.2 is supposed to go GA prior to JDK 6 going GA. Whenever you're going GA > and relying on a component that isn't GA, you're going to run in to trouble.
So... what *exactly* do you need from JDK 6 if it isn't a JDBC4 jar to compile against?
