From 21ed48267e8e0832478334373f984f941b14b865 Mon Sep 17 00:00:00 2001 From: bepo23 Date: Fri, 15 May 2009 09:09:06 +0000 Subject: [PATCH] git-svn-id: svn://svn.code.sf.net/p/wiigee/code/trunk@67 c7eff9ee-dd40-0410-8832-91a4d88773cf --- build.xml | 103 ++++++++++++++++++++++++++++++++++++------------------ 1 file changed, 69 insertions(+), 34 deletions(-) diff --git a/build.xml b/build.xml index f54e686..612f84d 100644 --- a/build.xml +++ b/build.xml @@ -1,39 +1,74 @@ - - - wiigee ant buildfile - - - - - - + + + + + + + + + + + Builds, tests, and runs the project JavaLibrary6. + + - - - - + 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: - - - - \ No newline at end of file + + + + + + + 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: + + + + + + + + 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. + + --> +