Brutex
/
XServices
1
0
Fork 0
Code Issues 2 Pull Requests Actions Projects Releases 4 Wiki Activity

Cleanup documentation build 

git-svn-id: https://brutex.net/svn/xservices/trunk@62 e7e49efb-446e-492e-b9ec-fcafc1997a86
tag-20130205r
Brian Rosenberger 2011-05-02 18:10:49 +00:00
parent 2aaf50fca1
commit 2e99ff8f80
1 changed files with 37 additions and 71 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

108
build.xml
View File

@ -1,71 +1,37 @@
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0"?>
<!-- You may freely edit this file. See commented blocks below for --> <project default="create-doc" basedir=".">
<!-- some examples of how to customize the build. -->
<!-- (If you delete it and reopen the project it will be recreated.) --> <property name="current-loc" location="." />
<!-- By default, only the Clean and Build commands use this build script. --> <property name="workspace" location=".." />
<!-- Commands such as Run, Debug, and Test only use this build script if --> <property name="htmldir" value="${current-loc}/doc/html" />
<!-- the Compile on Save feature is turned off for the project. --> <property name="docbookdir" value="C:\JAVA-DEV\docbook-xsl-ns-1.76.1\html\" />
<!-- You can turn off the Compile on Save (or Deploy on Save) setting --> <property name="docbooksource" value="${current-loc}/doc"/>
<!-- in the project's Project Properties dialog box.--> <property name="xalan" value="org.apache.xalan.processor.TransformerFactoryImpl" />
<project name="XServices" default="default" basedir=".">
<description>Builds, tests, and runs the project XServices.</description>
<import file="nbproject/build-impl.xml"/> <!-- XSLT Chunking Properties -->
<!-- <property name="base.dir" value="${htmldir}"/>
There exist several targets which are by default empty and which can be <target name="merge">
used for execution of your tasks. These targets are usually executed <xsl.xinclude in="${docbooksource}/BruteXServices_User_Guide.xml"
before and after some main targets. They are: out="${docbooksource}/BruteXServices_User_Guide.dbk"
/>
-pre-init: called before initialization of project properties </target>
-post-init: called after initialization of project properties
-pre-compile: called before javac compilation <target name="clean-doc">
-post-compile: called after javac compilation <delete dir="${htmldir}" />
-pre-compile-single: called before javac compilation of single file <mkdir dir="${htmldir}"/>
-post-compile-single: called after javac compilation of single file </target>
-pre-compile-test: called before javac compilation of JUnit tests
-post-compile-test: called after javac compilation of JUnit tests <target name="create-doc" depends="clean-doc, merge">
-pre-compile-test-single: called before javac compilation of single JUnit test
-post-compile-test-single: called after javac compilation of single JUunit test <xslt force="true" style="${docbookdir}/../toHTML.xsl"
-pre-dist: called before archive building in="${docbooksource}/BruteXServices_User_Guide.dbk"
-post-dist: called after archive building out="${htmldir}/index.html">
-post-clean: called after cleaning build products <factory name="${xalan}" />
-pre-run-deploy: called before deploying <param name="base.dir" expression="${htmldir}/"/>
-post-run-deploy: called after deploying <param name="use.id.as.filename" expression="1" />
</xslt>
Example of pluging an obfuscator after the compilation could look like </target>
<target name="-post-compile"> </project>
<obfuscate>
<fileset dir="${build.classes.dir}"/>
</obfuscate>
</target>
For list of available properties check the imported
nbproject/build-impl.xml file.
Other way how to customize the build is by overriding existing main targets.
The target 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
do-dist: archive building
run: execution of project
javadoc-build: javadoc generation
Example of overriding the target for project execution could look like
<target name="run" depends="<PROJNAME>-impl.jar">
<exec dir="bin" executable="launcher.exe">
<arg file="${dist.jar}"/>
</exec>
</target>
Notice that overridden target depends on jar target and not only on
compile target as regular run target does. Again, for list of available
properties which you can use check the target you are overriding in
nbproject/build-impl.xml file.
-->
</project>