Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <20228735.1154712734836.JavaMail.jira@brutus>
Date: Fri, 4 Aug 2006 10:32:14 -0700 (PDT)
From: "Rick Hillegas (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-1639) Include early-draft notice required by
 JDBC 4 spec license in NOTICES, release notes and documentation
In-Reply-To: <33404100.1154625133857.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/DERBY-1639?page=all ]

Rick Hillegas updated DERBY-1639:
---------------------------------

    Description: 
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.


  was:
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.


> 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