ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Diane Holt <hol...@yahoo.com>
Subject RE: problem with propertyfile task
Date Wed, 03 Oct 2001 18:36:46 GMT
--- Chuck.Irvine@mail.sprint.com wrote:
> ouch. messy workaround. i'll wait for the new functionality. thanks. 

Not so messy really -- you only had 4 properties that needed a default,
right? So, before your <propertyfile> task, you'd just need to add:

<property file="${classes.home}/com/sprint/fms/constants.properties"/>
<property name="CICS_TRANSACTION_GATEWAY_HOST" value="199.14.219.100"/>
<property name="CICS_TRANSACTION_GATEWAY_PORT" value="2006"/>
<property name="CICS_SERVER_NAME" value="DA131"/>
<property name="CICS_PROGRAM_NAME" value="FHXM0P"/>

and change the <entry>s for those properties in your <propertyfile> task
to
reference the property names instead:
     
<propertyfile
   file="${classes.home}/com/sprint/fms/constants.properties">
     <entry key="CICS_TRANSACTION_GATEWAY_HOST"
	    value="${CICS_TRANSACTION_GATEWAY_HOST}"/>
     <entry key="CICS_TRANSACTION_GATEWAY_PORT"
            value="${CICS_TRANSACTION_GATEWAY_PORT}"/>
     <entry key="CICS_SERVER_NAME"
            value="${CICS_SERVER_NAME}"/>
     <entry key="CICS_PROGRAM_NAME"
            value="${CICS_PROGRAM_NAME}"/>
     ...
</propertyfile>

If any of the properties are defined on the command-line, that's the value
they'll be given in the properties file. Or, if they're not defined on the
command-line, but are already in the properties file (assuming it exists),
that's the value they'll stay at. Otherwise, they'll be set to your
default values.

Diane

=====
(holtdl@yahoo.com)



__________________________________________________
Do You Yahoo!?
Listen to your Yahoo! Mail messages from any phone.
http://phone.yahoo.com

Mime
View raw message