Return-Path: <tfenne@rcn.com>
Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm
Delivered-To: mailing list ant-dev@jakarta.apache.org
Received: (qmail 88599 invoked from network); 24 Jul 2000 03:44:07 -0000
Received: from smtp02.mrf.mail.rcn.net (207.172.4.61)
  by locus.apache.org with SMTP; 24 Jul 2000 03:44:07 -0000
Received: from r83aap006110.sbo.ma.cable.rcn.com ([209.6.196.75] helo=cow)
	by smtp02.mrf.mail.rcn.net with smtp (Exim 3.15 #2)
	id 13GZ9z-0000yp-00
	for ant-dev@jakarta.apache.org; Sun, 23 Jul 2000 23:44:07 -0400
From: "Tim Fennell" <tfenne@rcn.com>
To: <ant-dev@jakarta.apache.org>
Subject: RE: Available task and JDK versions
Date: Sun, 23 Jul 2000 23:43:48 -0400
Message-ID: <PAEMIGABCOEPGKCJKAIDGEAICBAA.tfenne@rcn.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <85256926.000C0C10.00@d54mta04.raleigh.ibm.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N

That seems like a reasonable short term solution. But wouldn't it be better to
have a clearer approach? And one that won't require changes when the next
version of the JDK comes out?

Anyhows, I couldn't sleep, so here is the patch! (See next email).

-t
-----Original Message-----
From: rubys@us.ibm.com [mailto:rubys@us.ibm.com]
Sent: Sunday, July 23, 2000 22:03
To: ant-dev@jakarta.apache.org
Subject: Re: Available task and JDK versions




The following will do the trick today:

<available property="jdk.1.1" classname="java.lang.Void" />
<available property="jdk.1.2" classname="java.lang.ThreadLocal" />
<available property="jdk.1.3" classname="java.lang.StrictMath" />

- Sam Ruby