Put all the target associated with the properties into a new subbuild.xml and call it with <ant antfile="subbuild.xml"> � <property name="jar.file" value="blah.jar"/> </ant> <ant antfile="subbuild.xml"> � <property name="jar.file" value="blah_blah.jar" /> </ant> Just don't get jar.file before your ant tasks. �See the docs (index.html) for more details. Glenn McAllister TID - Software Developer - VisualAge for Java IBM Toronto Lab, (416) 448-3805 "An approximate answer to the right question is better than the right answer to the wrong question." - John W. Tukey Please respond to [EMAIL PROTECTED] To: � � � [EMAIL PROTECTED] cc: Subject: � � � �Questions [IMAGE] I've been experimenting with ant and I would like to suggest a feature (maybe someone is working on it or have thoughts on it etc). I would like to have an include tag (which references another generic xml build file) that gets included into the build file (this is the same with the include keyword for makefiles). I'm finding myself writing the exact same rules for a number of project with the name of the jar file being different. A question: where can I find an example of a more complex system using ant (eg having a top level build file with constructs subproject files and each subproject have build files that have dependencies between subprojects)? dino (Embedded image moved to file: pic28807.pcx)
pic28807.pcx
Description: Binary data
