| 1 |
<?xml version="1.0" encoding="UTF-8"?>
|
1 |
<?xml version="1.0"?>
|
| 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 |
<!-- By default, only the Clean and Build commands use this build script. -->
|
- |
|
| 6 |
<!-- Commands such as Run, Debug, and Test only use this build script if -->
|
- |
|
| 7 |
<!-- the Compile on Save feature is turned off for the project. -->
|
- |
|
| 8 |
<!-- You can turn off the Compile on Save (or Deploy on Save) setting -->
|
- |
|
| 9 |
<!-- in the project's Project Properties dialog box.-->
|
- |
|
| 10 |
<project name="XServices" default="default" basedir=".">
|
2 |
<project default="create-doc" basedir=".">
|
| 11 |
<description>Builds, tests, and runs the project XServices.</description>
|
- |
|
| 12 |
<import file="nbproject/build-impl.xml"/>
|
- |
|
| 13 |
<!--
|
- |
|
| 14 |
|
- |
|
| 15 |
There exist several targets which are by default empty and which can be
|
- |
|
| 16 |
used for execution of your tasks. These targets are usually executed
|
- |
|
| 17 |
before and after some main targets. They are:
|
- |
|
| 18 |
|
- |
|
| 19 |
-pre-init: called before initialization of project properties
|
- |
|
| 20 |
-post-init: called after initialization of project properties
|
- |
|
| 21 |
-pre-compile: called before javac compilation
|
- |
|
| 22 |
-post-compile: called after javac compilation
|
- |
|
| 23 |
-pre-compile-single: called before javac compilation of single file
|
- |
|
| 24 |
-post-compile-single: called after javac compilation of single file
|
- |
|
| 25 |
-pre-compile-test: called before javac compilation of JUnit tests
|
- |
|
| 26 |
-post-compile-test: called after javac compilation of JUnit tests
|
- |
|
| 27 |
-pre-compile-test-single: called before javac compilation of single JUnit test
|
- |
|
| 28 |
-post-compile-test-single: called after javac compilation of single JUunit test
|
- |
|
| 29 |
-pre-dist: called before archive building
|
- |
|
| 30 |
-post-dist: called after archive building
|
- |
|
| 31 |
-post-clean: called after cleaning build products
|
- |
|
| 32 |
-pre-run-deploy: called before deploying
|
- |
|
| 33 |
-post-run-deploy: called after deploying
|
- |
|
| 34 |
|
- |
|
| 35 |
Example of pluging an obfuscator after the compilation could look like
|
- |
|
| 36 |
|
- |
|
| 37 |
<target name="-post-compile">
|
- |
|
| 38 |
<obfuscate>
|
- |
|
| 39 |
<fileset dir="${build.classes.dir}"/>
|
- |
|
| 40 |
</obfuscate>
|
- |
|
| 41 |
</target>
|
- |
|
| - |
|
3 |
|
| - |
|
4 |
<property name="current-loc" location="." />
|
| - |
|
5 |
<property name="workspace" location=".." />
|
| - |
|
6 |
<property name="htmldir" value="${current-loc}/doc/html" />
|
| 42 |
|
7 |
<property name="docbookdir" value="C:\JAVA-DEV\docbook-xsl-ns-1.76.1\html\" />
|
| - |
|
8 |
<property name="docbooksource" value="${current-loc}/doc"/>
|
| - |
|
9 |
<property name="xalan" value="org.apache.xalan.processor.TransformerFactoryImpl" />
|
| - |
|
10 |
|
| 43 |
For list of available properties check the imported
|
11 |
|
| - |
|
12 |
<!-- XSLT Chunking Properties -->
|
| - |
|
13 |
<property name="base.dir" value="${htmldir}"/>
|
| - |
|
14 |
|
| - |
|
15 |
<target name="merge">
|
| - |
|
16 |
<xsl.xinclude in="${docbooksource}/BruteXServices_User_Guide.xml"
|
| - |
|
17 |
out="${docbooksource}/BruteXServices_User_Guide.dbk"
|
| - |
|
18 |
/>
|
| - |
|
19 |
</target>
|
| - |
|
20 |
|
| - |
|
21 |
<target name="clean-doc">
|
| - |
|
22 |
<delete dir="${htmldir}" />
|
| 44 |
nbproject/build-impl.xml file.
|
23 |
<mkdir dir="${htmldir}"/>
|
| 45 |
|
- |
|
| 46 |
|
24 |
</target>
|
| 47 |
Other way how to customize the build is by overriding existing main targets.
|
25 |
|
| 48 |
The target of interest are:
|
- |
|
| 49 |
|
26 |
<target name="create-doc" depends="clean-doc, merge">
|
| 50 |
init-macrodef-javac: defines macro for javac compilation
|
- |
|
| 51 |
init-macrodef-junit: defines macro for junit execution
|
- |
|
| 52 |
init-macrodef-debug: defines macro for class debugging
|
- |
|
| 53 |
do-dist: archive building
|
- |
|
| 54 |
run: execution of project
|
- |
|
| 55 |
javadoc-build: javadoc generation
|
27 |
|
| 56 |
|
28 |
<xslt force="true" style="${docbookdir}/../toHTML.xsl"
|
| 57 |
Example of overriding the target for project execution could look like
|
29 |
in="${docbooksource}/BruteXServices_User_Guide.dbk"
|
| 58 |
|
30 |
out="${htmldir}/index.html">
|
| 59 |
<target name="run" depends="<PROJNAME>-impl.jar">
|
31 |
<factory name="${xalan}" />
|
| 60 |
<exec dir="bin" executable="launcher.exe">
|
- |
|
| 61 |
<arg file="${dist.jar}"/>
|
- |
|
| 62 |
</exec>
|
- |
|
| 63 |
</target>
|
- |
|
| 64 |
|
- |
|
| 65 |
Notice that overridden target depends on jar target and not only on
|
- |
|
| 66 |
compile target as regular run target does. Again, for list of available
|
32 |
<param name="base.dir" expression="${htmldir}/"/>
|
| 67 |
properties which you can use check the target you are overriding in
|
33 |
<param name="use.id.as.filename" expression="1" />
|
| 68 |
nbproject/build-impl.xml file.
|
34 |
</xslt>
|
| 69 |
|
35 |
</target>
|
| 70 |
-->
|
36 |
|
| 71 |
</project>
|
37 |
</project>
|