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