ansaurus

Question

Answer 1

A:

CLASSPATH should be set inside the build.xml itself. If you're depending on a CLASSPATH environment variable, you're making a mistake.

See if this build.xml works better. Study the directory structure and make yours match that spelled out in the build.xml:

<?xml version="1.0" encoding="UTF-8"?>
<project name="xslt-converter" basedir="." default="package">

    <property name="version" value="1.6"/>
    <property name="haltonfailure" value="no"/>

    <property name="out" value="out"/>

    <property name="production.src" value="src"/>
    <property name="production.lib" value="lib"/>
    <property name="production.resources" value="config"/>
    <property name="production.classes" value="${out}/production/${ant.project.name}"/>

    <property name="test.src" value="test"/>
    <property name="test.lib" value="lib"/>
    <property name="test.resources" value="config"/>
    <property name="test.classes" value="${out}/test/${ant.project.name}"/>

    <property name="exploded" value="out/exploded/${ant.project.name}"/>
    <property name="exploded.classes" value="${exploded}/WEB-INF/classes"/>
    <property name="exploded.lib" value="${exploded}/WEB-INF/lib"/>

    <path id="production.class.path">
        <pathelement location="${production.classes}"/>
        <pathelement location="${production.resources}"/>
        <fileset dir="${production.lib}">
            <include name="**/*.jar"/>
            <exclude name="**/junit*.jar"/>
            <exclude name="**/*test*.jar"/>
        </fileset>
    </path>

    <path id="test.class.path">                            
        <path refid="production.class.path"/>
        <pathelement location="${test.classes}"/>
        <pathelement location="${test.resources}"/>
        <fileset dir="${test.lib}">
            <include name="**/junit*.jar"/>
            <include name="**/*test*.jar"/>
        </fileset>
    </path>

    <path id="testng.class.path">
        <fileset dir="${test.lib}">
            <include name="**/testng*.jar"/>
        </fileset>
    </path>

    <available file="${out}" property="outputExists"/>

    <target name="clean" description="remove all generated artifacts" if="outputExists">
        <delete dir="${out}" includeEmptyDirs="true"/>
        <delete dir="${reports.out}" includeEmptyDirs="true"/>
    </target>

    <target name="create" description="create the output directories" unless="outputExists">
        <mkdir dir="${production.classes}"/>
        <mkdir dir="${test.classes}"/>
        <mkdir dir="${reports.out}"/>
        <mkdir dir="${junit.out}"/>
        <mkdir dir="${testng.out}"/>
        <mkdir dir="${exploded.classes}"/>
        <mkdir dir="${exploded.lib}"/>
    </target>

    <target name="compile" description="compile all .java source files" depends="create">
        <!-- Debug output
                <property name="production.class.path" refid="production.class.path"/>
                <echo message="${production.class.path}"/>
        -->
        <javac srcdir="src" destdir="${out}/production/${ant.project.name}" debug="on" source="${version}">
            <classpath refid="production.class.path"/>
            <include name="**/*.java"/>
            <exclude name="**/*Test.java"/>
        </javac>
        <javac srcdir="${test.src}" destdir="${out}/test/${ant.project.name}" debug="on" source="${version}">
            <classpath refid="test.class.path"/>
            <include name="**/*Test.java"/>
        </javac>
    </target>

</project>

duffymo 2010-08-03 23:57:07

I am using a path in the build.xml, not writing out the CLASSPATH. What I meant was that running ant with debug prints out the CLASSPATH that is passed to javac, which has around 50 jars in it (big project).I also added the target from my build.xml.

Periodic 2010-08-04 00:17:12

Try my build.xml and see if it does any better.

duffymo 2010-08-04 00:26:23

I tried a simpler build.xml. Stripping out all but the javac (and there were a lot of targets and steps for a full build on this project) but unfortunately, no luck. I ended up setting the whole project up in Eclipse and that seems to have been successful.

Periodic 2010-08-05 16:30:39

Did you try the build.xml that I gave you?

duffymo 2010-08-05 18:20:32

Answer 2

A:

Can you run your ant build in debug mode so that you can step through it? Set a break point in your build.xml. Then Right click on the build.xml and select Debug As -> Ant Build (assuming you are using Eclipse). This might help you to figure out your issue.

HTH.

CoolBeans 2010-08-04 01:49:19

I wasn't using Eclipse at the time. the debug flag didn't help much.I did end up setting up the whole project in eclipse and eclipse was able to build it successfully.

Periodic 2010-08-05 16:31:14

okay if you could build it using eclipse, then you should make sure your paths in the build.xml are identical to the one that eclipse has set in the project properties (.classpath file of the project).

CoolBeans 2010-08-05 19:04:05

ansaurus

tags:

views:

answers:

Ant build fails with no visible errors

related questions