Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 17635 invoked from network); 19 Sep 2006 10:31:09 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 19 Sep 2006 10:31:09 -0000 Received: (qmail 84334 invoked by uid 500); 19 Sep 2006 10:30:29 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 84168 invoked by uid 500); 19 Sep 2006 10:30:28 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 84107 invoked by uid 99); 19 Sep 2006 10:30:28 -0000 Received: from idunn.apache.osuosl.org (HELO idunn.apache.osuosl.org) (140.211.166.84) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Sep 2006 03:30:28 -0700 X-ASF-Spam-Status: No, hits=0.0 required=5.0 tests= Received: from ([209.237.227.198:50943] helo=brutus.apache.org) by idunn.apache.osuosl.org (ecelerity 2.1 r(10620)) with ESMTP id 3E/00-26148-3C6CF054 for ; Tue, 19 Sep 2006 03:30:27 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 178DE7142F7 for ; Tue, 19 Sep 2006 10:26:52 +0000 (GMT) Message-ID: <8748281.1158661612094.JavaMail.jira@brutus> Date: Tue, 19 Sep 2006 03:26:52 -0700 (PDT) From: "John H. Embretsen (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-1846) Create a script that allows users to easily update their Derby jars with the JDBC4 classes. In-Reply-To: <31359127.1158175643656.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/DERBY-1846?page=comments#action_12435742 ] John H. Embretsen commented on DERBY-1846: ------------------------------------------ I tried the 'update-with-jdbc4' script on a Solaris box (default shell is bash), and it failed with the message "The JVM in $JAVA_HOME is not version 1.6.0 To use this script to compile the JDBC 4.0 Derby classes, you need a 1.6.0 level VM" But $JAVA_HOME was indeed set to a JDK 1.6 installation before running the script. There seems to be a problem with the following check in the script: if [ -z "$JAVA_HOME" ]; then if [ -n "$darwin" ]; then JAVA_HOME=/System/Library/Frameworks/JavaVM.framework/Home fi else if [ -d /usr/j2se -a -x /usr/j2se/bin/javac ]; then JAVA_HOME=/usr/j2se fi fi I say this because in my environment, JAVA_HOME is always set to /usr/j2se by the script (I added an echo statement to verify this), and since that location contains a JDK 1.4.2 installation, the subsequent version check fails (I later modified the script so that it would echo something if the first condition shown above is true. It did not, meaning that JAVA_HOME was set, but that the script modified it anyway). Perhaps an if - elif - fi construct may be more usable in the Bourne shell? > Create a script that allows users to easily update their Derby jars with the JDBC4 classes. > ------------------------------------------------------------------------------------------- > > Key: DERBY-1846 > URL: http://issues.apache.org/jira/browse/DERBY-1846 > Project: Derby > Issue Type: Improvement > Components: Demos/Scripts > Affects Versions: 10.2.1.0 > Reporter: Andrew McIntyre > Assigned To: Andrew McIntyre > Fix For: 10.2.1.0 > > Attachments: derby-1846-v1.diff, derby-1846-v2.diff > > > Since the resolution of the JDBC 4 licensing issue was to not ship a build that includes Derby's JDBC 4 code, but continue to ship the Derby source files for them, a script which automatically compiles and updates the Derby jars with the JDBC 4 classes would be useful. -- 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