ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Rich" <>
Subject RE: Property is set, but to what?
Date Wed, 21 Jul 2004 15:23:20 GMT
I would guess that the value of prop1 is null.  Try using <if> <equals
arg1="${prop1}" arg2=""/>... to see if that helps.

Thanks.  Bill 

Bill Rich
Wilandra Consulting LLC
1325 Addiewell Place
San Jose, CA  95120-3905
phone:      +1 408 268-2452
mobile:     +1 408 410-9713
Santa Cruz: +1 831 464-9007
fax:        +1 413 669-9716 or 

-----Original Message-----
From: Reeves, Paul C [] 
Sent: Wednesday, July 21, 2004 7:47 AM
To: ''
Subject: Property is set, but to what?


Does anyone know what happens when a property is set via a property file,
but there is nothing on the right-hand side of the equals sign?

prop1	=	
prop2	=	value2

When I load these properties then

<isset property="prop1">

returns "true"

If I echo the value held by the property:

<echo message="prop1 = (${prop1})"/>

I get:

prop1 = ()		(i.e., nothing shows up between parentheses)

I need to be able to test for this condition via ant contrib's <if> task,
but I cannot figure out what to compare to:

  <equals arg1="${prop1}" arg2="???"

I've tried 

      <equals arg1="${prop1}" arg2="&#x0a;"/>
      <equals arg1="${prop1}" arg2="&#13;"/>
      <equals arg1="${prop1}" arg2="&#9;"/>
      <equals arg1="${prop1}" arg2="&#32;"/>
      <equals arg1="${prop1}" arg2="false"/>

which I believe are:

    Line Feed
    Carriage Return

respectively, but none of these  seem to work.

Any idea what the prop1 actually holds?


P.S.  New Mexico State Motto:  "Carpe Manana"

To unsubscribe, e-mail: For additional
commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message