[ http://issues.apache.org/jira/browse/DERBY-1639?page=comments#action_12425901 ] Craig Russell commented on DERBY-1639: --------------------------------------
IANAL, but I don't think there is a problem. Derby is not an application. The only way you can run Derby that exposes JDBC4 functionality is by running a User Application with Java SE 6. If a User Application runs in this environment, is is subject to the testing and evaluation terms of the license. So there is no need to encumber Derby NOTICEs with this disclaimer. > Include early-draft notice required by JDBC 4 spec license in NOTICES, > release notes and documentation > ------------------------------------------------------------------------------------------------------ > > Key: DERBY-1639 > URL: http://issues.apache.org/jira/browse/DERBY-1639 > Project: Derby > Issue Type: Bug > Components: Documentation > Affects Versions: 10.2.0.0 > Reporter: Andrew McIntyre > Assigned To: Rick Hillegas > Fix For: 10.2.0.0 > > Attachments: derby-1639-notice_v01.diff, derby-1639-notice_v02.diff > > > from the license: > 3. Distribute applications written to the > Specification to third parties for their testing and > evaluation use, provided that any such application > includes the following notice: > "This is an application written to interoperate > with an early-draft specification developed under the > Java Community Process (JCP) and is made available for > testing and evaluation purposes only. The code is not > compatible with any specification of the JCP." > This notice needs to be included in the NOTICES file, and should also be used > to frame discussion of JDBC 4.0 features in the release notes and > documentation. > Here is a RELEASE NOTE for inclusion with this issue. I am editting this note > into the Description field so that we can amend it if necessary: > ----------------- RELEASE NOTE -------------------- > PROBLEM: > Derby 10.2 exposes an implementation of an early draft version of the JDBC4 > specification. > SYMPTOM: > This issue only affects you if you are running the Derby network client or > embedded server on Java SE 6. This issue does not affect you if you are > running Derby on J2SE 1.3, 1.4, or 1.5. > When run on Java SE 6, Derby's network client and embedded server expose JDBC > implementations which do not conform to an approved, final version of the > JDBC specification. Instead, these implementations adhere to an early-draft > version of the JDBC4 specification. Please note the following: > This is an application written to interoperate with an early-draft > specification developed under the Java Community Process (JCP) and is made > available for testing and evaluation purposes only. The code is not > compatible with any specification of the JCP. > SOLUTION: > A follow-on release will expose JDBC4 implementations conforming to the final > draft of the JDBC4 specification. > WORKAROUND: > If you do not want to use experimental, early-draft JDBC4 interfaces, run > Derby on J2SE 1.3, 1.4, or 1.5 or on J2ME/CDC/Foundation 1.0. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
