Return-Path: 
 <ant-user-return-10798-apmail-jakarta-ant-user-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-ant-user-archive@jakarta.apache.org
Received: (qmail 84509 invoked by uid 500); 27 Jul 2001 17:42:26 -0000
Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Post: <mailto:ant-user@jakarta.apache.org>
List-Help: <mailto:ant-user-help@jakarta.apache.org>
List-Unsubscribe: <mailto:ant-user-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:ant-user-subscribe@jakarta.apache.org>
Reply-To: ant-user@jakarta.apache.org
Delivered-To: mailing list ant-user@jakarta.apache.org
Received: (qmail 84470 invoked from network); 27 Jul 2001 17:42:25 -0000
X-Authentication-Warning: bodewig.bost.de: bodewig set sender to
 bodewig@apache.org using -f
To: ant-user@jakarta.apache.org
Subject: Re: does ant 1.3 work with jdk 1.4?
References: <Greg McDermott's message of "Fri, 27 Jul 2001 10:12:34 -0400">
	<4.3.1.2.20010727101056.03b96a58@nashua.beasys.com>
	<4.3.1.2.20010727105345.03de6628@nashua.beasys.com>
From: Stefan Bodewig <bodewig@apache.org>
Date: 27 Jul 2001 17:17:05 +0200
In-Reply-To: Greg McDermott's message of "Fri, 27 Jul 2001 10:58:27 -0400"
Message-ID: <m3wv4uz9ji.fsf@bodewig.bost.de>
Lines: 21
User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Cuyahoga Valley)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N

On Fri, 27 Jul 2001, Greg McDermott <gregm@bea.com> wrote:

> It might be seeing something similar, was it a compile time problem?

Just to clarify: it is no Ant problem, but one with our production
code.

Part of the problem is a compile time problem, we've created yet
another database pool and changes to the interfaces break it.

Things like Connection.setSavepoint that returns an instance of the
new Safepoint interface are going to give you similar headaches that
you may have encountered when they introduced JDBC 2.0 (err, 2.1 core)
- you cannot write a Connection class that is JDBC 3.0 compatible and
can be compiled on a JDK 1.3 system at the same time (without playing
tricks with the bootclasspath, that is).

And I'm sure we'd face all sorts of runtime errors as well, as the
drivers we use won't be JDBC 3.0 compatible either.

Stefan