[jira] Commented: (DERBY-1639) Include early-draft notice required by JDBC 4 spec license in NOTICES, release notes and documentation
[ http://issues.apache.org/jira/browse/DERBY-1639?page=comments#action_12425779 ] Daniel John Debrunner commented on DERBY-1639: -- Don't we have to respect Sun's naming scheme for jdk 1.6 and use Java SE 6? http://java.sun.com/developer/technicalArticles/JavaOne2005/naming.html What part of that text is required by the JCP? Does it any way mean that Derby is effectively not released under the Apache Licene v2.? I'm wondering what adding made available for testing an evaluation purposes only adds when the whole work is AS-IS under section 7 of the ALv2, and is that a restriction that is not acceptable? 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 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 jdk1.6. This issue does not affect you if you are running Derby on jdk1.3, jdk1.4, or jdk1.5. When run on jdk1.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: Run Derby on jdk1.3, jdk1.4, or jdk1.5 if you do not want to use experimental, early-draft JDBC4 interfaces. -- 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
[jira] Commented: (DERBY-1639) Include early-draft notice required by JDBC 4 spec license in NOTICES, release notes and documentation
[ http://issues.apache.org/jira/browse/DERBY-1639?page=comments#action_12425781 ] Daniel John Debrunner commented on DERBY-1639: -- Sorry, I see the extract that is required by the JCP licence. Still don't understand what that means wrt ALv2. 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 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 jdk1.6. This issue does not affect you if you are running Derby on jdk1.3, jdk1.4, or jdk1.5. When run on jdk1.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: Run Derby on jdk1.3, jdk1.4, or jdk1.5 if you do not want to use experimental, early-draft JDBC4 interfaces. -- 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
[jira] Commented: (DERBY-1639) Include early-draft notice required by JDBC 4 spec license in NOTICES, release notes and documentation
[ http://issues.apache.org/jira/browse/DERBY-1639?page=comments#action_12425797 ] Daniel John Debrunner commented on DERBY-1639: -- It probably depends on what the made available refers to. I read it as the Derby release itself,, and thus Derby can only be used for testing and evaluation. This seems to be against the ALv2. Can you take this question to legal-discuss? Ie. is it ok for the NOTICE file to have this text (restriction?). 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: Run Derby on J2SE 1.3, 1.4, or 1.5 if you do not want to use experimental, early-draft JDBC4 interfaces. -- 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
[jira] Commented: (DERBY-1639) Include early-draft notice required by JDBC 4 spec license in NOTICES, release notes and documentation
[ http://issues.apache.org/jira/browse/DERBY-1639?page=comments#action_12425798 ] Daniel John Debrunner commented on DERBY-1639: -- The release note should also include J2ME/CDC/Foundation 1.0 when it lists the list of Java environments. 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: Run Derby on J2SE 1.3, 1.4, or 1.5 if you do not want to use experimental, early-draft JDBC4 interfaces. -- 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
[jira] Commented: (DERBY-1639) Include early-draft notice required by JDBC 4 spec license in NOTICES, release notes and documentation
[ http://issues.apache.org/jira/browse/DERBY-1639?page=comments#action_12425819 ] Rick Hillegas commented on DERBY-1639: -- Before taking this to legal-discuss, maybe I could sand down the verbiage a bit to make it clear that the experimental nature of the JDBC api only applies if you are running Derby on Java SE 6: When run on Java SE 6, this application exposes an implementation of an early-draft version of JDBC4, an interface through which Java applications communicate with databases. When run on Java SE 6: 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 when run on Java SE 6. With these changes, do you think that there is a conflict with the ALv2? 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
[jira] Commented: (DERBY-1639) Include early-draft notice required by JDBC 4 spec license in NOTICES, release notes and documentation
[ http://issues.apache.org/jira/browse/DERBY-1639?page=comments#action_12425835 ] Daniel John Debrunner commented on DERBY-1639: -- -1 on this change until it has been cleared through the legal-discuss and the DB-PMC. Rick, I believe it might conflict with the ALv2, but I'm not a lawyer, that's why I think it should go to legal-discuss. It seems like the notice is restricting use of Derby which seems to me to be in conflict. 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
[jira] Commented: (DERBY-1639) Include early-draft notice required by JDBC 4 spec license in NOTICES, release notes and documentation
[ 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
Re: [jira] Commented: (DERBY-1639) Include early-draft notice required by JDBC 4 spec license in NOTICES, release notes and documentation
+1, I think what Craig says here makes sense. There is no way anybody can legally run in production with JDBC4 until Java SE 6 is declared GA. David Craig Russell (JIRA) wrote: [ 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.
Re: [jira] Commented: (DERBY-1639) Include early-draft notice required by JDBC 4 spec license in NOTICES, release notes and documentation
David Van Couvering wrote: +1, I think what Craig says here makes sense. not sure This sentence seems unrelated to what Craig said. There is no way anybody can legally run in production with JDBC4 until Java SE 6 is declared GA. I think this fact is irrelvant, once Java SE 6 goes GA, the Derby 10.2 release would still be available and it can't have the testing/evaluation limitation on it. Dan.
