<?xml version="1.0" encoding="UTF-8"?>
<!-- You may freely edit this file. See commented blocks below for -->
<!-- some examples of how to customize the build. -->
<!-- (If you delete it and reopen the project it will be recreated.) -->
<project name="polydiff" default="default" basedir=".">
    <description>Builds, tests, and runs the project polydiff.</description>
    <import file="nbproject/build-impl.xml"/>
    <!--

    There exist several targets which are by default empty and which can be
    used for execution of your tasks. These targets are usually executed
    before and after some main targets. They are:

      -pre-init:                 called before initialization of project properties
      -post-init:                called after initialization of project properties
      -pre-compile:              called before javac compilation
      -post-compile:             called after javac compilation
      -pre-compile-single:       called before javac compilation of single file
      -post-compile-single:      called after javac compilation of single file
      -pre-compile-test:         called before javac compilation of JUnit tests
      -post-compile-test:        called after javac compilation of JUnit tests
      -pre-compile-test-single:  called before javac compilation of single JUnit test
      -post-compile-test-single: called after javac compilation of single JUunit test
      -pre-jar:                  called before JAR building
      -post-jar:                 called after JAR building
      -post-clean:               called after cleaning build products

    (Targets beginning with '-' are not intended to be called on their own.)

    Example of inserting an obfuscator after compilation could look like this:

        <target name="-post-compile">
            <obfuscate>
                <fileset dir="${build.classes.dir}"/>
            </obfuscate>
        </target>

    For list of available properties check the imported
    nbproject/build-impl.xml file.


    Another way to customize the build is by overriding existing main targets.
    The targets of interest are:

      -init-macrodef-javac:     defines macro for javac compilation
      -init-macrodef-junit:     defines macro for junit execution
      -init-macrodef-debug:     defines macro for class debugging
      -init-macrodef-java:      defines macro for class execution
      -do-jar-with-manifest:    JAR building (if you are using a manifest)
      -do-jar-without-manifest: JAR building (if you are not using a manifest)
      run:                      execution of project
      -javadoc-build:           Javadoc generation
      test-report:              JUnit report generation

    An example of overriding the target for project execution could look like this:

        <target name="run" depends="polydiff-impl.jar">
            <exec dir="bin" executable="launcher.exe">
                <arg file="${dist.jar}"/>
            </exec>
        </target>

    Notice that the overridden target depends on the jar target and not only on
    the compile target as the regular run target does. Again, for a list of available
    properties which you can use, check the target you are overriding in the
    nbproject/build-impl.xml file.

    -->
    <!-- Do not forget to place the archive containing the antlr3 task, namely
         "ant-antlr3.jar" in the ant/lib directory. The path to the ant home
         directory can be found/configured in netbeans via the
         Tools->Options->Miscellaneous->ant sheet.
         
         The antlr jar file (e.g. antlr-3.3-complete.jar) itself has to be added to the
         Compile-time libraries via the Project-Properties dialog. 
    -->
    <!-- where to place the antlr generated files -->
    <property name="src" location="src"/>
    <!-- name of the package -->
    <property name="package" value=""/>
    <!-- where to find the grammar files -->
    <property name="grammar" location="grammar"/>
    <!-- where to write/find token files -->
    <property name="token.lib" location="${src}/${package}" />

    <!-- a convenience macro which invokes antlr -->
    <macrodef name="antlr3">
        <attribute name="grammar.name"/>
        <attribute name="package" default="${package}"/>
        <attribute name="multithreaded" default="True"/>
        <attribute name="verbose" default="True"/>
        <attribute name="debug" default="False"/>
        <sequential>
            <echo message="antlr ${grammar}/@{grammar.name}" />
            <antlr:ant-antlr3 xmlns:antlr="antlib:org/apache/tools/ant/antlr"
                  target="${grammar}/@{grammar.name}"
                  outputdirectory="${src}/@{package}"
                  libdirectory="${src}/@{package}"
                  multithreaded="@{multithreaded}"
                  verbose="@{verbose}"
                  debug="@{debug}">
                <classpath>
                    <pathelement path="${javac.classpath}"/>
                </classpath>
            </antlr:ant-antlr3>
        </sequential>
    </macrodef>

    <!-- Modify here. Adapt the dependencies for your grammar(s).
         Watch out to specify the dependencies in the correct order!
         The sequence in which the grammars are compiled by Antlr in
         this example:
         1: Poly.g as PolyDifferentiator depends on it
         2: PolyDifferentiator as Simplifier dependends on it
         3: Simplifier.g as PolyPrinter dependends on it
         4: PolyPrinter.g
    -->
    <target name="-pre-compile" depends="PolyPrinter"/>
    <target name="PolyPrinter" depends="Simplifier">
        <antlr3 grammar.name="PolyPrinter.g"/>
    </target>
    <target name="Simplifier" depends="PolyDifferentiator">
        <antlr3 grammar.name="Simplifier.g"/>
    </target>
    <target name="PolyDifferentiator" depends="Poly">
        <antlr3 grammar.name="PolyDifferentiator.g"/>
    </target>
    <target name="Poly">
        <antlr3 grammar.name="Poly.g"/>
    </target>

</project>