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

97
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. -->
<!-- Commands such as Run, Debug, and Test only use this build script if -->
<!-- the Compile on Save feature is turned off for the project. -->
<!-- You can turn off the Compile on Save (or Deploy on Save) setting -->
<!-- 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"/>
<!--
<!-- set global properties for this build --> There exist several targets which are by default empty and which can be
<property name="src" location="src"/> used for execution of your tasks. These targets are usually executed
<property name="build" location="build"/> before and after some main targets. They are:
<property name="dist" location="dist"/>
<target name="init"> -pre-init: called before initialization of project properties
<!-- Create the time stamp --> -post-init: called after initialization of project properties
<tstamp/> -pre-compile: called before javac compilation
<!-- Create the build directory structure used by compile --> -post-compile: called after javac compilation
<mkdir dir="${build}"/> -pre-compile-single: called before javac compilation of single file
</target> -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="build" depends="init" (Targets beginning with '-' are not intended to be called on their own.)
description="compile the source " >
<!-- Compile the java code from ${src} into ${build} -->
<javac srcdir="${src}" destdir="${build}"/>
</target>
<target name="jar" depends="build" Example of inserting an obfuscator after compilation could look like this:
description="generate the distribution" >
<!-- Create the distribution directory -->
<mkdir dir="${dist}"/>
<!-- Put everything in ${build} into the wiigee-${DSTAMP}.jar file --> <target name="-post-compile">
<jar jarfile="${dist}/wiigee-${DSTAMP}.jar" basedir="${build}"/> <obfuscate>
<fileset dir="${build.classes.dir}"/>
</obfuscate>
</target>
<!-- Copy this release to wiigee_current.jar --> For list of available properties check the imported
<copy file="${dist}/wiigee-${DSTAMP}.jar" tofile="${release}/wiigee_current.jar"/> nbproject/build-impl.xml file.
</target>
<target name="clean" description="clean up" >
<delete dir="${build}"/> Another way to customize the build is by overriding existing main targets.
</target> 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> </project>