Jean T. Anderson wrote: > David Van Couvering wrote: > >>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". > > excellent correction -- thanks. > >>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. > > JDBC 3 will still be the default with the Java SE 6 final release? Ok; > probably I didn't follow some discussions closely enough.
sorry, I see exactly what you mean now -- and it's actually what prompted me to push out that first revision. How does this sound (still need to nail down build-it-yourself info): 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 was not available when this release was produced. JDBC 3.0 will be available by default when used with a Java SE 6 virtual machine. JDBC 4.0 functionality will only be available to developers who download Java SE 6 themselves and build Derby with it [more info TBD, maybe include reference to Andrew's script, or maybe to a wiki page?]. getting better? thanks, -jean > >>"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? > > > Good question. Andrew is working on a script [1]. If that jells, maybe > this wording could mention that. > > >>Also, once they build in JDBC4 support, will JDBC4 be the default when >>running with a Java SE 6 VM? > > > Up above you said the JDBC 3 is still the default, so I'm confused. > > -jean > > [1] > http://mail-archives.apache.org/mod_mbox/db-derby-dev/200609.mbox/[EMAIL > PROTECTED] > > >>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 >>> >>> >
