Return-Path: 
 <ant-user-return-26689-qmlist-jakarta-archive-ant-user=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-ant-user-archive@apache.org
Received: (qmail 83987 invoked from network); 10 Nov 2002 17:00:26 -0000
Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131)
  by daedalus.apache.org with SMTP; 10 Nov 2002 17:00:26 -0000
Received: (qmail 7079 invoked by uid 97); 10 Nov 2002 17:01:14 -0000
Delivered-To: qmlist-jakarta-archive-ant-user@jakarta.apache.org
Received: (qmail 7014 invoked by uid 97); 10 Nov 2002 17:01:13 -0000
Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:ant-user-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:ant-user-subscribe@jakarta.apache.org>
List-Help: <mailto:ant-user-help@jakarta.apache.org>
List-Post: <mailto:ant-user@jakarta.apache.org>
List-Id: "Ant Users List" <ant-user.jakarta.apache.org>
Reply-To: "Ant Users List" <ant-user@jakarta.apache.org>
Delivered-To: mailing list ant-user@jakarta.apache.org
Received: (qmail 6887 invoked by uid 98); 10 Nov 2002 17:01:12 -0000
X-Antivirus: nagoya (v4218 created Aug 14 2002)
X-Originating-IP: [12.254.208.112]
Reply-To: "Martin" <webmaster@laconiadatasystems.com>
From: "Martin" <mgainty@hotmail.com>
To: "Ant Users List" <ant-user@jakarta.apache.org>
References: <1036881780.26586.8.camel@dolj>
 <009001c28843$83611800$25515b3f@kendall>
Subject: Re: Using available's property setting ability inside a condition,
 isit possible?
Date: Thu, 11 Apr 2002 09:57:35 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Message-ID: <OE36W7VUVSoErX5xhGV00002ae4@hotmail.com>
X-OriginalArrivalTime: 10 Nov 2002 17:00:12.0838 (UTC)
 FILETIME=[A2621460:01C288DA]
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

On a related note
How does one extend the classpath in java task
I set classpath as such
<java classpath="./lib/newjar.jar;${classpath}" ....
but I find this classpath specification does not work
I find that adding a property into global classpath works
Am I implementing classpath in java correctly?
Thank You,
Martin
----- Original Message -----
From: "Kendall Collett" <kcollett@convio.com>
To: "Ant Users List" <ant-user@jakarta.apache.org>
Sent: Saturday, November 09, 2002 6:58 PM
Subject: Re: Using available's property setting ability inside a condition,
isit possible?


> In the documentation for the nested elements of <condition> (see
> <http://jakarta.apache.org/ant/manual/CoreTasks/conditions.html>), it
says:
>     available
>     This condition is identical to the Available task, all attributes and
> nested elements of that task are supported, *the property and value
> attributes are redundant and will be ignored*.
>
> Kendall
>
> ----- Original Message -----
> From: "David Budworth" <dlbant@nustiu.net>
> To: "ANT User List" <ant-user@jakarta.apache.org>
> Sent: Saturday, November 09, 2002 16:43
> Subject: Using available's property setting ability inside a condition,
isit
> possible?
>
>
> > Hi All,
> >
> > I'm finding that the following doesn't work:
> > <target name="find.compiler">
> >   <condition property="compiler.found">
> >     <or>
> >       <available file="jikes" filepath="${env.PATH}"
> >          property="compiler.type" value="jikes"/>
> >       <available file="javac" filepath="${env.PATH}"
> >          property="compiler.type" value="javac"/>
> >     </or>
> >   </condition>
> >   <echo>Compiler found: ${compiler.found}, type: ${compiler.type}</echo>
> > </target>
> >
> > output:
> > [echo] Compiler found: true, type: ${compiler.type}
> >
> >
> > The compiler type never gets set.
> >
> > If I move the available directives outside the condition and comment out
> > the condition section I get:
> > [echo] Compiler found: ${compiler.found}, type: jikes
> >
> >
> > The ${compiler.found} part is expected in the second output since I
> > removed the condition.  But, as you can see, ${compiler.type} gets set
> > just fine.
> >
> > The only workaround for this I can find is to do it the old way, of
> > multiple targets with an "unless=compiler.type" tag on them.
> >
> > Is this a bug?  I found no mention in the docs for condition saying you
> > can't set properties inside it like that.
> >
> > Thank you
> > -David Budworth
> >
> >
> >
> >
> >
> >
> >
> >
> > --
> > To unsubscribe, e-mail:
<mailto:ant-user-unsubscribe@jakarta.apache.org>
> > For additional commands, e-mail:
<mailto:ant-user-help@jakarta.apache.org>
> >
>
>
>
> --
> To unsubscribe, e-mail:   <mailto:ant-user-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: <mailto:ant-user-help@jakarta.apache.org>
>

--
To unsubscribe, e-mail:   <mailto:ant-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-user-help@jakarta.apache.org>