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

Cleanup documentation build

Browse Source 
git-svn-id: https://brutex.net/svn/xservices/trunk@62 e7e49efb-446e-492e-b9ec-fcafc1997a86
This commit is contained in:
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

90
build.xml
View File

@ -1,71 +1,37 @@
<?xml version="1.0" encoding="UTF-8"?>
<!-- You may freely edit this file. See commented blocks below for -->
<!-- some examples of how to customize the build. -->
<!-- (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="XServices" default="default" basedir=".">
<description>Builds, tests, and runs the project XServices.</description>
<import file="nbproject/build-impl.xml"/>
<!--
<?xml version="1.0"?>
<project default="create-doc" basedir=".">
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-dist: called before archive building
-post-dist: called after archive building
-post-clean: called after cleaning build products
-pre-run-deploy: called before deploying
-post-run-deploy: called after deploying
Example of pluging an obfuscator after the compilation could look like
<target name="-post-compile">
<obfuscate>
<fileset dir="${build.classes.dir}"/>
</obfuscate>
</target>
For list of available properties check the imported
nbproject/build-impl.xml file.
<property name="current-loc" location="." />
<property name="workspace" location=".." />
<property name="htmldir" value="${current-loc}/doc/html" />
<property name="docbookdir" value="C:\JAVA-DEV\docbook-xsl-ns-1.76.1\html\" />
<property name="docbooksource" value="${current-loc}/doc"/>
<property name="xalan" value="org.apache.xalan.processor.TransformerFactoryImpl" />
Other way how to customize the build is by overriding existing main targets.
The target of interest are:
<!-- XSLT Chunking Properties -->
<property name="base.dir" value="${htmldir}"/>
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
<target name="merge">
<xsl.xinclude in="${docbooksource}/BruteXServices_User_Guide.xml"
out="${docbooksource}/BruteXServices_User_Guide.dbk"
/>
</target>
Example of overriding the target for project execution could look like
<target name="clean-doc">
<delete dir="${htmldir}" />
<mkdir dir="${htmldir}"/>
</target>
<target name="run" depends="<PROJNAME>-impl.jar">
<exec dir="bin" executable="launcher.exe">
<arg file="${dist.jar}"/>
</exec>
</target>
<target name="create-doc" depends="clean-doc, merge">
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.
<xslt force="true" style="${docbookdir}/../toHTML.xsl"
in="${docbooksource}/BruteXServices_User_Guide.dbk"
out="${htmldir}/index.html">
<factory name="${xalan}" />
<param name="base.dir" expression="${htmldir}/"/>
<param name="use.id.as.filename" expression="1" />
</xslt>
</target>
-->
</project>