Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <7643732.1146683628268.JavaMail.jira@brutus>
Date: Wed, 3 May 2006 19:13:48 +0000 (GMT+00:00)
From: "Andrew McIntyre (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-1078) Be able to build Derby when JAVA_HOME
 is set 1.6
In-Reply-To: <1348301538.1141689032204.JavaMail.jira@ajax>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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

Andrew McIntyre updated DERBY-1078:
-----------------------------------

    Attachment: derby-1078_part3.diff

Attaching patch3 to resolve the problem with the parsers in IBM JDK 1.3.1 mentioned above. I will commit this shortly if there are no objections.

> Be able to build Derby when JAVA_HOME is set 1.6
> ------------------------------------------------
>
>          Key: DERBY-1078
>          URL: http://issues.apache.org/jira/browse/DERBY-1078
>      Project: Derby
>         Type: Improvement

>   Components: Build tools
>     Versions: 10.2.0.0
>     Reporter: Rick Hillegas
>     Assignee: Andrew McIntyre
>      Fix For: 10.2.0.0
>  Attachments: derby-1078.diff, derby-1078_part2.diff, derby-1078_part3.diff
>
> Currently, the 1.4 compiler is used to build most of Derby. We use the 1.6 compiler to (optionally) build the JDBC4 support. If you try to build Derby in a shell window with a 1.6 JAVA_HOME, the 1.4 bits will fail to build. This is because those bits do not satisfy the JDBC4 contract. In addition, even if you could build those bits under 1.6, the 1.6 class files would fail to load on a 1.4 vm.
> We need to be able to use 1.6 as our default build environment but still generate jar files which run on 1.4 and 1.5. There may be compiler switches which allow this. If not, building in a 1.6 environment could fault in the 1.4 compiler as necessary.

-- 
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