rik/jlibwiigee
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

git-svn-id: svn://svn.code.sf.net/p/wiigee/code/trunk@67 c7eff9ee-dd40-0410-8832-91a4d88773cf

Browse Source
This commit is contained in:
bepo23
2009-05-15 09:09:06 +00:00
parent bc77857352
commit 21ed48267e
1 changed files with 69 additions and 34 deletions
Download Patch File Download Diff File Expand all files Collapse all files

103
build.xml
View File

@@ -1,39 +1,74 @@
<project name="wiigee-lib" default="jar" basedir="."> <?xml version="1.0" encoding="UTF-8"?>
<description> <!-- You may freely edit this file. See commented blocks below for -->
wiigee ant buildfile <!-- some examples of how to customize the build. -->
</description> <!-- (If you delete it and reopen the project it will be recreated.) -->
<!-- By default, only the Clean and Build commands use this build script. -->
<!-- set global properties for this build --> <!-- Commands such as Run, Debug, and Test only use this build script if -->
<property name="src" location="src"/> <!-- the Compile on Save feature is turned off for the project. -->
<property name="build" location="build"/> <!-- You can turn off the Compile on Save (or Deploy on Save) setting -->
<property name="dist" location="dist"/> <!-- in the project's Project Properties dialog box.-->
<project name="wiigee-lib" default="default" basedir=".">
<description>Builds, tests, and runs the project JavaLibrary6.</description>
<import file="nbproject/build-impl.xml"/>
<!--
<target name="init"> There exist several targets which are by default empty and which can be
<!-- Create the time stamp --> used for execution of your tasks. These targets are usually executed
<tstamp/> before and after some main targets. They are:
<!-- Create the build directory structure used by compile -->
<mkdir dir="${build}"/>
</target>
<target name="build" depends="init" -pre-init: called before initialization of project properties
description="compile the source " > -post-init: called after initialization of project properties
<!-- Compile the java code from ${src} into ${build} --> -pre-compile: called before javac compilation
<javac srcdir="${src}" destdir="${build}"/> -post-compile: called after javac compilation
</target> -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
<target name="jar" depends="build" (Targets beginning with '-' are not intended to be called on their own.)
description="generate the distribution" >
<!-- Create the distribution directory -->
<mkdir dir="${dist}"/>
<!-- Put everything in ${build} into the wiigee-${DSTAMP}.jar file --> Example of inserting an obfuscator after compilation could look like this:
<jar jarfile="${dist}/wiigee-${DSTAMP}.jar" basedir="${build}"/>
<!-- Copy this release to wiigee_current.jar -->
<copy file="${dist}/wiigee-${DSTAMP}.jar" tofile="${release}/wiigee_current.jar"/>
</target>
<target name="clean" description="clean up" > <target name="-post-compile">
<delete dir="${build}"/> <obfuscate>
</target> <fileset dir="${build.classes.dir}"/>
</project> </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="JavaLibrary6-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.
-->
</project>