Return-Path: 
 <ant-user-return-26711-qmlist-jakarta-archive-ant-user=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-ant-user-archive@apache.org
Received: (qmail 82530 invoked from network); 11 Nov 2002 16:44:57 -0000
Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131)
  by daedalus.apache.org with SMTP; 11 Nov 2002 16:44:57 -0000
Received: (qmail 21511 invoked by uid 97); 11 Nov 2002 16:45:46 -0000
Delivered-To: qmlist-jakarta-archive-ant-user@jakarta.apache.org
Received: (qmail 21495 invoked by uid 97); 11 Nov 2002 16:45:46 -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 21483 invoked by uid 98); 11 Nov 2002 16:45:45 -0000
X-Antivirus: nagoya (v4218 created Aug 14 2002)
Subject: Re: Using available's property setting ability inside a condition,
	is it possible?
From: David Budworth <dlbant@nustiu.net>
To: ANT User List <ant-user@jakarta.apache.org>
In-Reply-To: <m3vg34ec3g.fsf@bodewig.bost.de>
References: <1036881780.26586.8.camel@dolj>
	<m3vg34ec3g.fsf@bodewig.bost.de>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) 
Date: 11 Nov 2002 08:45:35 -0800
Message-Id: <1037033135.8078.16.camel@dolj>
Mime-Version: 1.0
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Actually, this is what I tried from the start
But you get a deprecation warning about using available to overwrite an
existing property

I ended up doing what's below.  Looking at it now though, I'm not sure
why ${found.compiler} doesn't get overwritten with javac after it's
found jikes (both are in my path).  But I'd guess that that's a feature
of condition (non-overriding).  At any rate, this lets you specify the
compiler (it assumes the compiler type is the same as the binary to
execute ie: jikes=jikes, javac=javac, won't work on windows), or will
auto-detect the jikes/javac for you.



<target name="find.compiler">
  <condition property="found.compiler" value="${compiler.type}">
    <and>
      <isset property="compiler.type"/>
      <available file="${compiler.type}" filepath="${env.PATH}"/>
    </and>
  </condition>
  <condition property="found.compiler" value="jikes">
    <and>
      <not>
        <isset property="compiler.type"/>
      </not>
      <available file="jikes" filepath="${env.PATH}"/>
    </and>
  </condition>
  <condition property="found.compiler" value="javac">
    <and>
      <not>
        <isset property="compiler.type"/>
      </not>
      <available file="javac" filepath="${env.PATH}"/>
    </and>
  </condition>
  <fail unless="found.compiler" if="compiler.type"
    message="Failed to find specified compiler: ${compiler.type}"/>
  <fail unless="found.compiler"
    message="Failed to find jikes or javac in your path"/>
  <property name="compiler.type" value="${found.compiler}"/>
  <echo>Compiler Type: ${compiler.type}</echo>
</target>


On Mon, 2002-11-11 at 00:37, Stefan Bodewig wrote:
> On 09 Nov 2002, David Budworth <dlbant@nustiu.net> wrote:
> 
> > 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.
> 
> So I'll try to help to find another one:
> 
>   <available file="jikes" filepath="${env.PATH}"
>      property="compiler.type" value="jikes"/>
>   <available file="javac" filepath="${env.PATH}"
>      property="compiler.type" value="javac"/>
>   <condition property="compiler.found">
>     <isset property="compiler.type"/>
>   </condition>
>   <echo>Compiler found: ${compiler.found}, type: ${compiler.type}</echo>
> 
> Stefan
> 
> --
> 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>