source: subversion/applications/editors/josm-ng/build.xml @ 34598

Last change on this file since 34598 was 6801, checked in by nenik, 12 years ago

Initial import of JOSMng sources. No style data yet.

File size: 3.3 KB
Line 
1<?xml version="1.0" encoding="UTF-8"?>
2<!-- You may freely edit this file. See commented blocks below for -->
3<!-- some examples of how to customize the build. -->
4<!-- (If you delete it and reopen the project it will be recreated.) -->
5<project name="josm-ng" default="default" basedir=".">
6    <description>Builds, tests, and runs the project josm-ng.</description>
7    <import file="nbproject/build-impl.xml"/>
8
9    <import file="nbproject/profiler-build-impl.xml"/>    <!--
10
11    There exist several targets which are by default empty and which can be
12    used for execution of your tasks. These targets are usually executed
13    before and after some main targets. They are:
14
15      -pre-init:                 called before initialization of project properties
16      -post-init:                called after initialization of project properties
17      -pre-compile:              called before javac compilation
18      -post-compile:             called after javac compilation
19      -pre-compile-single:       called before javac compilation of single file
20      -post-compile-single:      called after javac compilation of single file
21      -pre-compile-test:         called before javac compilation of JUnit tests
22      -post-compile-test:        called after javac compilation of JUnit tests
23      -pre-compile-test-single:  called before javac compilation of single JUnit test
24      -post-compile-test-single: called after javac compilation of single JUunit test
25      -pre-jar:                  called before JAR building
26      -post-jar:                 called after JAR building
27      -post-clean:               called after cleaning build products
28
29    (Targets beginning with '-' are not intended to be called on their own.)
30
31    Example of inserting an obfuscator after compilation could look like this:
32
33        <target name="-post-compile">
34            <obfuscate>
35                <fileset dir="${build.classes.dir}"/>
36            </obfuscate>
37        </target>
38
39    For list of available properties check the imported
40    nbproject/build-impl.xml file.
41
42
43    Another way to customize the build is by overriding existing main targets.
44    The targets of interest are:
45
46      -init-macrodef-javac:     defines macro for javac compilation
47      -init-macrodef-junit:     defines macro for junit execution
48      -init-macrodef-debug:     defines macro for class debugging
49      -init-macrodef-java:      defines macro for class execution
50      -do-jar-with-manifest:    JAR building (if you are using a manifest)
51      -do-jar-without-manifest: JAR building (if you are not using a manifest)
52      run:                      execution of project
53      -javadoc-build:           Javadoc generation
54      test-report:              JUnit report generation
55
56    An example of overriding the target for project execution could look like this:
57
58        <target name="run" depends="josm-ng-impl.jar">
59            <exec dir="bin" executable="launcher.exe">
60                <arg file="${dist.jar}"/>
61            </exec>
62        </target>
63
64    Notice that the overridden target depends on the jar target and not only on
65    the compile target as the regular run target does. Again, for a list of available
66    properties which you can use, check the target you are overriding in the
67    nbproject/build-impl.xml file.
68
69    -->
70</project>
Note: See TracBrowser for help on using the repository browser.