Mercurial > public > html2wiki

comparison build.xml @ 0:f8b1ea49d065

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Initial version of crude HTML to WikiText converter. Customized for converting HTML files from DEC Document into Wiki markup.
author smith@nwoca.org
date Fri, 12 May 2006 16:45:42 -0400
parents
children b6e94d49a9a9
comparison
equal deleted inserted replaced
-1:000000000000 0:f8b1ea49d065
1 <?xml version="1.0" encoding="UTF-8"?>
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 <project name="html2wiki" default="default" basedir=".">
6 <description>Builds, tests, and runs the project html2wiki.</description>
7 <import file="nbproject/build-impl.xml"/>
8
9 <property name="project.name" value="html2wiki" />
10 <property name="project.version" value="0.1-0" />
11
12 <property file="../../build.global"/>
13 <property name="ssdt.home.dir" value="../../"/>
14 <property name="tools.dir" value="${ssdt.home.dir}/Tools"/>
15 <import file="${tools.dir}/jalopy/ant/jalopy-ant.xml" optional="true"/>
16 <import file="${tools.dir}/checkstyle/ant/checkstyle-ant.xml"/>
17
18 <!--
19
20 There exist several targets which are by default empty and which can be
21 used for execution of your tasks. These targets are usually executed
22 before and after some main targets. They are:
23
24 -pre-init: called before initialization of project properties
25 -post-init: called after initialization of project properties
26 -pre-compile: called before javac compilation
27 -post-compile: called after javac compilation
28 -pre-compile-single: called before javac compilation of single file
29 -post-compile-single: called after javac compilation of single file
30 -pre-compile-test: called before javac compilation of JUnit tests
31 -post-compile-test: called after javac compilation of JUnit tests
32 -pre-compile-test-single: called before javac compilation of single JUnit test
33 -post-compile-test-single: called after javac compilation of single JUunit test
34 -pre-jar: called before JAR building
35 -post-jar: called after JAR building
36 -post-clean: called after cleaning build products
37
38 (Targets beginning with '-' are not intended to be called on their own.)
39
40 Example of inserting an obfuscator after compilation could look like this:
41
42 <target name="-post-compile">
43 <obfuscate>
44 <fileset dir="${build.classes.dir}"/>
45 </obfuscate>
46 </target>
47
48 For list of available properties check the imported
49 nbproject/build-impl.xml file.
50
51
52 Another way to customize the build is by overriding existing main targets.
53 The targets of interest are:
54
55 -init-macrodef-javac: defines macro for javac compilation
56 -init-macrodef-junit: defines macro for junit execution
57 -init-macrodef-debug: defines macro for class debugging
58 -init-macrodef-java: defines macro for class execution
59 -do-jar-with-manifest: JAR building (if you are using a manifest)
60 -do-jar-without-manifest: JAR building (if you are not using a manifest)
61 run: execution of project
62 -javadoc-build: Javadoc generation
63 test-report: JUnit report generation
64
65 An example of overriding the target for project execution could look like this:
66
67 <target name="run" depends="html2wiki-impl.jar">
68 <exec dir="bin" executable="launcher.exe">
69 <arg file="${dist.jar}"/>
70 </exec>
71 </target>
72
73 Notice that the overridden target depends on the jar target and not only on
74 the compile target as the regular run target does. Again, for a list of available
75 properties which you can use, check the target you are overriding in the
76 nbproject/build-impl.xml file.
77
78 -->
79 <!-- <target name="-pre-compile-single">
80 <antcall target="jalopy-single"/>
81 </target>
82 -->
83 </project>