Thanks, Jean.
A couple of things
"when used with a Java SE 6 beta build" - I think we should clarify this
by saying "when run with a Java SE 6 virtual machine". This will be
true whether the Java SE 6 they are using is beta or not, and I think it
is important to clarify this as runtime behavior.
"build Derby with it" - I hope a user doesn't have to build *all* of
Derby, but instead incrementally build in JDBC4 support such that it is
added to the existing jar files. Or is a complete rebuild required?
Also, once they build in JDBC4 support, will JDBC4 be the default when
running with a Java SE 6 VM?
David
Jean T. Anderson wrote:
Scratch that first attempt -- already caught an ambiguity. Second try:
This documentation references new JDBC 4.0 functionality that is not
enabled in this Apache Derby 10.2 release because a final Java SE 6
release is not available yet. JDBC 3.0 will be available by default when
used with a Java SE 6 beta build. JDBC 4.0 functionality will only be
available to developers who download Java SE 6 themselves and build
Derby with it.
-jean
Jean T. Anderson wrote:
I'm looking for wording we can plug into both the release notes and
strategic pages in the documentation. How does this sound?
This documentation references new JDBC 4.0 functionality that is not
enabled in this Apache Derby 10.2 release. Until a final Java SE 6
release is available, JDBC 3.0 will be available by default when used
with a Java SE 6 beta build. JDBC 4.0 functionality will only be
available to developers who download Java SE 6 themselves and build
Derby with it.
tweaks? comments? corrections?
thanks,
-jean
