Why not just put all of those properties in a .properties file and import them in each build script?
<property file="../default.properties"/> You can even further extend this approach by allowing the users to provide over-rides to these as follows: <property file="${env.USER_HOME_DIR}/default.properties"/> <property file="../default.properties"/> regards, d. -----Original Message----- From: Dave Rathnow [mailto:dave.rathnow@;wrx-ca.com] Sent: Friday, November 15, 2002 10:21 AM To: 'Ant Users List' Subject: RE: Can properties be returned to a calling ant script? > > 2. Can you have a called Ant script define properties which > > can be picked up by the calling Ant script. > > Write them to a file that gets read back in by the parent build > process. Most of the time, you don't want to do this 8-) Okay, I'll bite. Why isn't this a good idea? I would like to have a way that all common properties are set in a single build script so I don't have to modify all my build scripts if changes are made. Can you suggest another method? Thanks, Dave. -- 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>