Databases
StackOverflow2013
Postsdbo
POHow to execute Ant build in command line
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to execute Ant build in command line
    primarykey
    data
    text
    <p>I have an Ant build file, and I try to execute it in the command line with the following command:</p> <pre class="lang-bat prettyprint-override"><code>$ C:\Program Files (x86)\.....&gt;ant -f C:\Silk4J\Automation\iControlSilk4J\build.xml </code></pre> <p>But nothing happens, and the result is:</p> <pre><code>BUILD SUCCESSFUL Total time: 0 seconds </code></pre> <p>My environment variable is correct. <br/> What is the problem? Here is my build file:</p> <pre><code>&lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt; &lt;!-- WARNING: Eclipse auto-generated file. Any modifications will be overwritten. To include a user specific buildfile here, simply create one in the same directory with the processing instruction &lt;?eclipse.ant.import?&gt; as the first entry and export the buildfile again. --&gt; &lt;project basedir="." default="build" name="iControlSilk4J"&gt; &lt;property environment="env"/&gt; &lt;property name="ECLIPSE_HOME" value="../../../Program Files (x86)/Silk/SilkTest/eclipse"/&gt; &lt;property name="junit.output.dir" value="junit"/&gt; &lt;property name="debuglevel" value="source,lines,vars"/&gt; &lt;property name="target" value="1.6"/&gt; &lt;property name="source" value="1.6"/&gt; &lt;path id="Silk Test JTF 13.5.0 Library.libraryclasspath"&gt; &lt;pathelement location="../../../Program Files (x86)/Silk/SilkTest/ng/JTF/silktest-jtf-nodeps.jar"/&gt; &lt;/path&gt; &lt;path id="JUnit 4.libraryclasspath"&gt; &lt;pathelement location="${ECLIPSE_HOME}/plugins/org.junit_4.8.2.v4_8_2_v20110321-1705/junit.jar"/&gt; &lt;pathelement location="${ECLIPSE_HOME}/plugins/org.hamcrest.core_1.1.0.v20090501071000.jar"/&gt; &lt;/path&gt; &lt;path id="iControlSilk4J.classpath"&gt; &lt;pathelement location="bin"/&gt; &lt;pathelement location="lib/apache-log4j.jar"/&gt; &lt;pathelement location="lib/commons-io-2.4.jar"/&gt; &lt;pathelement location="lib/commons-lang3-3.1.jar"/&gt; &lt;pathelement location="lib/junit.jar"/&gt; &lt;pathelement location="lib/org.hamcrest.core_1.1.0.v20090501071000.jar"/&gt; &lt;pathelement location="lib/silktest-jtf-nodeps.jar"/&gt; &lt;path refid="Silk Test JTF 13.5.0 Library.libraryclasspath"/&gt; &lt;path refid="JUnit 4.libraryclasspath"/&gt; &lt;pathelement location="../../../Users/Admin/Desktop/java-mail-1.4.4.jar"/&gt; &lt;pathelement location="../../../Users/Admin/Desktop/javax.activation.jar"/&gt; &lt;pathelement location="lib/joda-time-2.3.jar"/&gt; &lt;/path&gt; &lt;target name="init"&gt; &lt;mkdir dir="bin"/&gt; &lt;copy includeemptydirs="false" todir="bin"&gt; &lt;fileset dir="src"&gt; &lt;exclude name="**/*.java"/&gt; &lt;/fileset&gt; &lt;/copy&gt; &lt;/target&gt; &lt;target name="clean"&gt; &lt;delete dir="bin"/&gt; &lt;/target&gt; &lt;target depends="clean" name="cleanall"/&gt; &lt;target depends="build-subprojects,build-project" name="build"/&gt; &lt;target name="build-subprojects"/&gt; &lt;target depends="init" name="build-project"&gt; &lt;echo message="${ant.project.name}: ${ant.file}"/&gt; &lt;javac debug="true" debuglevel="${debuglevel}" destdir="bin" source="${source}" target="${target}"&gt; &lt;src path="src"/&gt; &lt;classpath refid="iControlSilk4J.classpath"/&gt; &lt;/javac&gt; &lt;/target&gt; &lt;target description="Build all projects which reference this project. Useful to propagate changes." name="build-refprojects"/&gt; &lt;target description="copy Eclipse compiler jars to ant lib directory" name="init-eclipse-compiler"&gt; &lt;copy todir="${ant.library.dir}"&gt; &lt;fileset dir="${ECLIPSE_HOME}/plugins" includes="org.eclipse.jdt.core_*.jar"/&gt; &lt;/copy&gt; &lt;unzip dest="${ant.library.dir}"&gt; &lt;patternset includes="jdtCompilerAdapter.jar"/&gt; &lt;fileset dir="${ECLIPSE_HOME}/plugins" includes="org.eclipse.jdt.core_*.jar"/&gt; &lt;/unzip&gt; &lt;/target&gt; &lt;target description="compile project with Eclipse compiler" name="build-eclipse-compiler"&gt; &lt;property name="build.compiler" value="org.eclipse.jdt.core.JDTCompilerAdapter"/&gt; &lt;antcall target="build"/&gt; ... </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USGuylene Emond
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COGlad you pasted the build file in, but you omitted some important portions. Notice that the project tag has "build" as the default. To help you, we will need to see definition of the target named "build".
      singulars
      1. POHow to execute Ant build in command line
      1. USjoescii
    2. COIs that what you talk about ?<project basedir="." default="build" name="iControlSilk4J"> ?!?
      singulars
      1. POHow to execute Ant build in command line
      1. USGuylene Emond
    3. COYes, that indicates that the `build` target is the default. Which means that somewhere in your build file, there is a `<target name="build"/>` tag we need to see.
      singulars
      1. POHow to execute Ant build in command line
      1. USjoescii
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload