Return-Path: Delivered-To: apmail-db-jdo-dev-archive@www.apache.org Received: (qmail 4735 invoked from network); 3 Apr 2006 17:00:26 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 3 Apr 2006 17:00:26 -0000 Received: (qmail 47001 invoked by uid 500); 3 Apr 2006 17:00:23 -0000 Mailing-List: contact jdo-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jdo-dev@db.apache.org Delivered-To: mailing list jdo-dev@db.apache.org Received: (qmail 46990 invoked by uid 99); 3 Apr 2006 17:00:23 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Apr 2006 10:00:23 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Apr 2006 10:00:23 -0700 Received: from ajax (localhost.localdomain [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id 1009ED49FE for ; Mon, 3 Apr 2006 18:00:02 +0100 (BST) Message-ID: <1206649913.1144083602062.JavaMail.jira@ajax> Date: Mon, 3 Apr 2006 18:00:02 +0100 (BST) From: "Craig Russell (JIRA)" To: jdo-dev@db.apache.org Subject: [jira] Created: (JDO-360) Update information on JDK 1.3 jta jar MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Update information on JDK 1.3 jta jar ------------------------------------- Key: JDO-360 URL: http://issues.apache.org/jira/browse/JDO-360 Project: JDO Type: Task Components: tck20, site and infrastructure Reporter: Craig Russell Priority: Trivial The jdo project is running an old version of the jta jar: geronimo-spec geronimo-spec-jta 1.0.1B-rc2 The new version is org.apache.geronimo.specs geronimo-jta_1.0.1B_spec 1.0 The reason we use this jar instead of the Sun distribution is to allow maven directly to load the jar, which is impossible under the Sun license. There is no harm in changing to the new jar, so we should probably do this in the trunk. I found we are using this old version issue while trying to figure out if the new jar supports JDK 1.3. But the new jar doesn't either. See below. We document in http://wiki.apache.org/jdo/J2SESupport that we don't support 1.3 and give instructions on how to download the 1.3 version from the Sun web site. It might be an idea to update this page with instructions on how to tell maven to use this jar instead of the geronimo jar, but I think there are already clues about what to do. Proposed action: 1. Update project.xml in trunk to refer to the new geronimo jar. 2. Update wiki with latest information on how to use the Sun 1.3 distribution. -20- 5 api20 >java -version java version "1.3.1_18" Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_18-b01) Java HotSpot(TM) Client VM (build 1.3.1_18-b01, mixed mode) 6 api20 >maven java:compile __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0.2 Attempting to download geronimo-jta_1.0.1B_spec-1.0.jar. 11K downloaded build:start: java:prepare-filesystem: [mkdir] Created dir: C:\users\michael\jdo\workspaces\jdo\trunk\api20\target\classes java:compile: [echo] Compiling to c:\users\michael\jdo\workspaces\jdo\trunk\api20/target/classes [javac] Compiling 58 source files to C:\users\michael\jdo\workspaces\jdo\trunk\api20\target\classes C:\users\michael\jdo\workspaces\jdo\trunk\api20\src\java\javax\jdo\Transaction.java:23: cannot access javax.transaction.Synchronization bad class file: C:\users\michael\.maven\repository\org.apache.geronimo.specs\jars\geronimo-jta_1.0.1B_spec-1.0.jar(javax/transaction/Synchronization.class) class file has wrong version 48.0, should be 47.0 Please remove or make sure it appears in the correct subdirectory of the classpath. import javax.transaction.Synchronization; ^ 1 error BUILD FAILED -- 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