Well, I do use this property in another target if/unless attribute. So I
used Diane Holt suggestion below:
<target name="awregister.manifest-up2date?">
<condition property="awregister.manifest-up2date">
<and>
<available property="classes-dir-exists"
file="${classes}"
type="dir" />
<uptodate targetfile="${awregistration.manifest}">
<srcfiles dir="${classes}"
includes="com/lgc/mowi/pres/**/*.class" />
</uptodate>
</and>
</condition>
<!-- All this to print "true" or "false" for the property value -->
<condition property="awregister.manifest-up2date.value"
value="false">
<equals arg1="${awregister.manifest-up2date}"
arg2="$${awregister.manifest-up2date}" />
</condition>
<property name="awregister.manifest-up2date.value"
value="true" />
<echo message="awregister.manifest-up2date =
${awregister.manifest-up2date.value}" />
</target><!-- awregister.manifest-up2date? -->
-----Original Message-----
From: Stefan Bodewig [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 14, 2002 10:04 AM
To: [EMAIL PROTECTED]
Subject: Re: Better property handling...
On Mon, 11 Feb 2002, Dominique Devienne <[EMAIL PROTECTED]> wrote:
> Ideally, I would like to see false instead of
> ${awregister.manifest-up2date}!
Assuming you don't want to use the property for if/unless attributes:
> <condition property="awregister.manifest-up2date">
> <and>
> <available property="classes-dir-exists"
> file="${classes}"
> type="dir" />
> <uptodate targetfile="${awregistration.manifest}">
> <srcfiles dir="${classes}"
> includes="com/lgc/mowi/pres/**/*.class" />
> </uptodate>
> </and>
> </condition>
<property name="awregister.manifest-up2date" value="false" />
> <echo message="awregister.manifest-up2date =
${awregister.manifest-up2date}" />
will do the trick.
Stefan
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
