12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091929394959697 |
- <?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.) -->
- <project name="DMDirc" default="default" basedir=".">
- <description>Builds, tests, and runs the project DMDirc.</description>
- <import file="nbproject/build-impl.xml"/>
- <import file="BuildPlugins.xml"/>
- <!--
-
- 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-jar: called before JAR building
- -post-jar: called after JAR building
- -post-clean: called after cleaning build products
-
- (Targets beginning with '-' are not intended to be called on their own.)
-
- Example of inserting an obfuscator after compilation could look like this:
-
- <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.
-
-
- Another way to customize the build is by overriding existing main targets.
- 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="DMDirc-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.
- <jar compress="${jar.compress}" jarfile="${build.classes.dir}/plugins/">
- <fileset dir="${build.classes.dir}"/>
- </jar>
- -->
- <target name="-post-compile" depends="build-plugins"/>
-
- <available file="/bin/bash" property="has.bash"/>
-
- <target name="installer" depends="installer-nobuild, installer-build"/>
-
- <target name="installer-build" if="has.bash">
- <exec executable="/bin/bash" dir="installer" resultproperty="installer.result">
- <arg value="release.sh"/>
- <arg value="this"/>
- </exec>
-
- <condition property="installer.success">
- <equals arg1="${installer.result}" arg2="0" />
- </condition>
-
- <echo message="Installer build finished."/>
- <echo message="Completed build files can be found in:"/>
- <echo message=" ${installer.output.dir}"/>
- <echo message=""/>
- </target>
-
- <target name="installer-nobuild" unless="has.bash">
- <echo message="This task only works on linux"/>
- </target>
- </project>
|