ant-contrib’s Variable task can do this: <property name=”x” value=”6″/> <echo>${x}</echo> <!– will print 6 –> <var name=”x” unset=”true”/> <property name=”x” value=”12″/> <echo>${x}</echo> <!– will print 12 –> Not recommended, though, it can lead to weird side-effects if parts of your Ant scripts assume immutable property values, and other parts break this assumption.
You could create your own script for running ant, e.g. named ant.sh like: #!/bin/sh JAVA_HOME=</path/to/jdk>; export JAVA_HOME ant $@ and then run your script. $ chmod 755 ant.sh $./ant.sh clean compile or whatever ant target you wish to run
Have you tried using the zipfileset task? <jar destfile=”stripped.jar”> <zipfileset src=”full.jar” excludes=”files/to/exclude/**/*.file” /> </jar> Example <property name=”library.dir” value=”dist” /> <property name=”library.file” value=”YourJavaArchive.jar” /> <property name=”library.path” value=”${library.dir}/${library.file}” /> <property name=”library.path.new” value=”${library.dir}/new-${library.file}” /> <target name=”purge-superfluous”> <echo>Removing superfluous files from Java archive.</echo> <jar destfile=”${library.path.new}”> <zipfileset src=”${library.path}” excludes=”**/ComicSans.ttf” /> </jar> <delete file=”${library.path}” /> <move file=”${library.path.new}” tofile=”${library.path}” /> </target>
The initial problem with your set up is that you’ve got build.properties and build-defaults.properties reversed. Ant Properties are set once and then can never be overridden. That’s why setting any property on the command line via a -Dproperty=value will always override anything you’ve set in the file; the property is set and then nothing can … Read more
I’ve just run into the same problem. I haven’t tried it yet, but I plan to include versions of swt.jar for all platforms and load the correct one dynamically in the start of the main method. UPDATE: It worked. build.xml includes all jars: <zipfileset dir=”/home/aromanov/workspace/foo/lib” includes=”swt_linux_gtk_x86.jar”/> <zipfileset dir=”/home/aromanov/workspace/foo/lib” includes=”swt_macosx_x86.jar”/> <zipfileset dir=”/home/aromanov/workspace/foo/lib” includes=”swt_win32_x86.jar”/> <zipfileset dir=”/home/aromanov/workspace/foo/lib” includes=”swt_linux_gtk_x64.jar”/> … Read more
The echo task in ANT is able to write to files <echo file=”output.txt” append=”true”> abc=${abc} </echo>
You can use the Condition task with an isset condition. <project default=”test”> <property name=”a” value=”a”/> <target name=”test”> <condition property=”a.set” else=”false”> <isset property=”a”/> </condition> <condition property=”b.set” else=”false”> <isset property=”b”/> </condition> <echo message=”a set ? ${a.set}”/> <echo message=”b set ? ${b.set}”/> </target> </project> Output: test: [echo] a set ? true [echo] b set ? false
The following approach works for me: <exclude name=”**/dir_name_to_exclude/**” />
You can use conditions using the <fail> task: <fail message=”Property "foo" needs to be set to a value”> <condition> <or> <equals arg1=”${foo}” arg2=””/> <not> <isset property=”foo”/> </not> </or> </condition> This is equivalent to saying if (not set ${foo} or ${foo} = “”) is pseudocode. You have to read the XML conditions from the inside out. … Read more
For this specific case, I’m not going to answer the question “how to find if a directory exists”, because that’s already been answered, but I’m just going to point out that in your clean task you can use failonerror=”false” to keep the ant task from exiting. This should be suitable in a clean task because … Read more