Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 22802 invoked from network); 21 Sep 2006 15:22:04 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 21 Sep 2006 15:22:04 -0000 Received: (qmail 57546 invoked by uid 500); 21 Sep 2006 15:22:03 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 57355 invoked by uid 500); 21 Sep 2006 15:22:02 -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 57346 invoked by uid 99); 21 Sep 2006 15:22:02 -0000 Received: from idunn.apache.osuosl.org (HELO idunn.apache.osuosl.org) (140.211.166.84) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Sep 2006 08:22:02 -0700 X-ASF-Spam-Status: No, hits=0.0 required=5.0 tests= Received: from [209.237.227.198] ([209.237.227.198:55013] helo=brutus.apache.org) by idunn.apache.osuosl.org (ecelerity 2.1.1.8 r(12930)) with ESMTP id 7B/30-00858-A1EA2154 for ; Thu, 21 Sep 2006 08:22:02 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 77BEC4190CA for ; Thu, 21 Sep 2006 15:18:23 +0000 (GMT) Message-ID: <6600754.1158851903488.JavaMail.jira@brutus> Date: Thu, 21 Sep 2006 08:18:23 -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_12436552 ] John H. Embretsen commented on DERBY-1846: ------------------------------------------ I tried the script again (from an updated trunk) on Solaris 10 x86, bash shell (version 3.00.16), and after doing the double-to-quadruple-backslash fix (at two places in the script), I get the following error: --------8>--------------------------------------- Compiling the client classes for JDBC 4.0 /home/user/apache/Derby/clean/trunk/java/client/org/apache/derby/client/net/NetConnection.java:43: org.apache.derby.client.net.NetConnection is not abstract and does not override abstract method createStruct(java.lang.String,java.lang.Object[]) in java.sql.Connection public class NetConnection extends org.apache.derby.client.am.Connection { ^ Note: /home/user/apache/Derby/clean/trunk/java/client/org/apache/derby/client/net/NetConnection.java uses unchecked or unsafe operations. Note: Recompile with -Xlint:unchecked for details. 1 error There was an error compiling the client classes. Exiting. --------8>--------------------------------------- Not sure yet what is causing this. Could it be a user error? I hope someone else is able to try it on Solaris as well... I also tried the updated batch script on Win XP, and it went fine - at least the jdbc40 suite passes in both Embedded and DerbyNetClient frameworks. The only thing I wanted to comment is that the script started out by reporting "The system cannot find the file specified", which is caused by trying to remove a %DERBY_HOME%\jdbc4classes directory that does not exist yet. No big deal, its just something that may scare users (unless it is documented properly). > 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, derby1846-batchFix_v1.diff, modules.properties, output_batchFix_v1.txt > > > 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