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
Here’s a simple and quick answer to Mavenizing an Ant project: DON’T DO IT! This is not some anti-Maven screed. I use Maven, and I like Maven. It forces developers not to do stupid things. Developers are terrible at writing build scripts. They want to do things this way and not the way everyone else … Read more
The following approach works for me: <exclude name=”**/dir_name_to_exclude/**” />
Since what you’re wanting to do is add dependency management to an existing Ant project, that’s precisely what Ivy’s designed to do. Dependency management is a big part of Maven, but far from all of it. Maven is more of a project-oriented tool that does several other things in addition to dependencies. It would be … Read more
It sounds like you have it setup right. What happens if you try something like this, which worked for me: C:\>set ANT_HOME=C:\apache-ant-1.8.1 C:\>set JAVA_HOME=C:\jdk1.6.0_24 C:\>set PATH=%ANT_HOME%\bin;%JAVA_HOME%\bin C:\>ant -version Apache Ant version 1.8.1 compiled on April 30 2010 This also worked for me by setting up environment variables, like so:
You are getting the error related to classID. This is a concept described in detail at JaCoCo docs-site. http://www.eclemma.org/jacoco/trunk/doc/classids.html. This is a key step for supporting multiple versions of class (an appserver for example) in same JVM. Copying part some part of it here for visibility. What are class ids and how are they created? … Read more
If you have Ant version < 1.8.3 (ant -version) try this approach for the issue with JDK 7 (based on the previous answer): Add signjarjdk7 to ANDROID_SDK\tools\ant\build.xml <macrodef name=”signjarjdk7″> <attribute name=”jar” /> <attribute name=”signedjar” /> <attribute name=”keystore” /> <attribute name=”storepass” /> <attribute name=”alias” /> <attribute name=”keypass” /> <attribute name=”verbose” /> <sequential> <exec executable=”jarsigner” failonerror=”true”> <!– … Read more
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
build.xml usually is an ant build script. It contains information necessary to build the project to produce the desired output, be it Javadocs, a compiled project, or a JAR file. I believe Eclipse has ant built-in, so it should be possible to execute the build.xml by choosing “Run As…” and “Ant Build”. The build.xml file, … Read more
It really depends. Maven and Ant are just different approaches: imperative and declarative (see Imperative vs Declarative build systems) Maven is better for managing dependencies (but Ant is ok with them too, if you use Ant+Ivy) and build artefacts. The main benefit from maven – its lifecycle. You can just add specific actions on correct … Read more