java/nekurak.net-lib/build.xml
author František Kučera <franta-hg@frantovo.cz>
Mon Nov 07 20:31:08 2011 +0100 (2011-11-07)
changeset 196 27b751390163
permissions -rw-r--r--
XSD: lepší schéma pro komentáře a povolíme blockquote.
franta-hg@132
     1
<?xml version="1.0" encoding="UTF-8"?>
franta-hg@132
     2
<!-- You may freely edit this file. See commented blocks below for -->
franta-hg@132
     3
<!-- some examples of how to customize the build. -->
franta-hg@132
     4
<!-- (If you delete it and reopen the project it will be recreated.) -->
franta-hg@132
     5
<!-- By default, only the Clean and Build commands use this build script. -->
franta-hg@132
     6
<!-- Commands such as Run, Debug, and Test only use this build script if -->
franta-hg@132
     7
<!-- the Compile on Save feature is turned off for the project. -->
franta-hg@132
     8
<!-- You can turn off the Compile on Save (or Deploy on Save) setting -->
franta-hg@132
     9
<!-- in the project's Project Properties dialog box.-->
franta-hg@132
    10
<project name="nekurak.net-lib" default="default" basedir=".">
franta-hg@132
    11
    <description>Builds, tests, and runs the project nekurak.net-lib.</description>
franta-hg@132
    12
    <import file="nbproject/build-impl.xml"/>
franta-hg@132
    13
    <!--
franta-hg@132
    14
franta-hg@132
    15
    There exist several targets which are by default empty and which can be 
franta-hg@132
    16
    used for execution of your tasks. These targets are usually executed 
franta-hg@132
    17
    before and after some main targets. They are: 
franta-hg@132
    18
franta-hg@132
    19
      -pre-init:                 called before initialization of project properties
franta-hg@132
    20
      -post-init:                called after initialization of project properties
franta-hg@132
    21
      -pre-compile:              called before javac compilation
franta-hg@132
    22
      -post-compile:             called after javac compilation
franta-hg@132
    23
      -pre-compile-single:       called before javac compilation of single file
franta-hg@132
    24
      -post-compile-single:      called after javac compilation of single file
franta-hg@132
    25
      -pre-compile-test:         called before javac compilation of JUnit tests
franta-hg@132
    26
      -post-compile-test:        called after javac compilation of JUnit tests
franta-hg@132
    27
      -pre-compile-test-single:  called before javac compilation of single JUnit test
franta-hg@132
    28
      -post-compile-test-single: called after javac compilation of single JUunit test
franta-hg@132
    29
      -pre-jar:                  called before JAR building
franta-hg@132
    30
      -post-jar:                 called after JAR building
franta-hg@132
    31
      -post-clean:               called after cleaning build products
franta-hg@132
    32
franta-hg@132
    33
    (Targets beginning with '-' are not intended to be called on their own.)
franta-hg@132
    34
franta-hg@132
    35
    Example of inserting an obfuscator after compilation could look like this:
franta-hg@132
    36
franta-hg@132
    37
        <target name="-post-compile">
franta-hg@132
    38
            <obfuscate>
franta-hg@132
    39
                <fileset dir="${build.classes.dir}"/>
franta-hg@132
    40
            </obfuscate>
franta-hg@132
    41
        </target>
franta-hg@132
    42
franta-hg@132
    43
    For list of available properties check the imported 
franta-hg@132
    44
    nbproject/build-impl.xml file. 
franta-hg@132
    45
franta-hg@132
    46
franta-hg@132
    47
    Another way to customize the build is by overriding existing main targets.
franta-hg@132
    48
    The targets of interest are: 
franta-hg@132
    49
franta-hg@132
    50
      -init-macrodef-javac:     defines macro for javac compilation
franta-hg@132
    51
      -init-macrodef-junit:     defines macro for junit execution
franta-hg@132
    52
      -init-macrodef-debug:     defines macro for class debugging
franta-hg@132
    53
      -init-macrodef-java:      defines macro for class execution
franta-hg@132
    54
      -do-jar-with-manifest:    JAR building (if you are using a manifest)
franta-hg@132
    55
      -do-jar-without-manifest: JAR building (if you are not using a manifest)
franta-hg@132
    56
      run:                      execution of project 
franta-hg@132
    57
      -javadoc-build:           Javadoc generation
franta-hg@132
    58
      test-report:              JUnit report generation
franta-hg@132
    59
franta-hg@132
    60
    An example of overriding the target for project execution could look like this:
franta-hg@132
    61
franta-hg@132
    62
        <target name="run" depends="nekurak.net-lib-impl.jar">
franta-hg@132
    63
            <exec dir="bin" executable="launcher.exe">
franta-hg@132
    64
                <arg file="${dist.jar}"/>
franta-hg@132
    65
            </exec>
franta-hg@132
    66
        </target>
franta-hg@132
    67
franta-hg@132
    68
    Notice that the overridden target depends on the jar target and not only on 
franta-hg@132
    69
    the compile target as the regular run target does. Again, for a list of available 
franta-hg@132
    70
    properties which you can use, check the target you are overriding in the
franta-hg@132
    71
    nbproject/build-impl.xml file. 
franta-hg@132
    72
franta-hg@132
    73
    -->
franta-hg@132
    74
</project>