<?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="pvvserver" default="default" basedir=".">
|
<description>Builds, tests, and runs the project pvvserver.</description>
|
<import file="nbproject/build-impl.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: JAR building
|
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="pvvserver-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.
|
|
-->
|
|
|
<target name="-post-jar">
|
<echo>Adding data files to jar...</echo>
|
|
<copy todir="build/classes">
|
<fileset dir="${basedir}">
|
<include name="data/**"/>
|
</fileset>
|
</copy>
|
|
<jar destfile="dist/pvvserver.jar" update="true">
|
<fileset dir="${basedir}">
|
<include name="data/**"/>
|
</fileset>
|
</jar>
|
|
<!--
|
The major number is increased when there are significant jumps in functionality
|
such as changing the framework which could cause incompatibility with interfacing systems
|
The minor number is incremented when only minor features or significant fixes have been added
|
The revision number is incremented when minor bugs are fixed
|
-->
|
|
<propertyfile file="${src.dir}\version.properties">
|
<entry key="date" type="date" value="now" pattern="dd/MM/yyyy" />
|
<entry key="major" type="int" value="1" />
|
<entry key="minor" type="int" value="0" />
|
<entry key="revision" type="int" value="0" />
|
<entry key="build" type="int" value="1" operation="+" />
|
</propertyfile>
|
|
|
<property name="store.jar.name" value="pvvserver"/>
|
|
<property name="store.dir" value="store"/>
|
<property name="store.jar" value="${store.dir}/${store.jar.name}.jar"/>
|
<echo message="Packaging ${application.title} into a single JAR at ${store.jar}"/>
|
|
<delete dir="${store.dir}"/>
|
<mkdir dir="${store.dir}"/>
|
<jar destfile="${store.dir}/temp_final.jar" filesetmanifest="skip">
|
<zipgroupfileset dir="dist" includes="*.jar"/>
|
<zipgroupfileset dir="dist/lib" includes="*.jar"/>
|
|
<manifest>
|
<attribute name="Main-Class" value="${main.class}"/>
|
</manifest>
|
</jar>
|
<zip destfile="${store.jar}">
|
<zipfileset src="${store.dir}/temp_final.jar"
|
excludes="META-INF/*.SF, META-INF/*.DSA, META-INF/*.RSA"/>
|
</zip>
|
<delete file="${store.dir}/temp_final.jar"/>
|
|
<echo message="Creating exe"/>
|
<property name="createExe" value="${basedir}\" />
|
<echo>${createIndex}</echo>
|
<exec dir="${createExe}" executable="cmd">
|
<arg line="/c jar2exe-console64.bat" />
|
</exec>
|
<exec dir="${createExe}" executable="cmd">
|
<arg line="/c jar2exe64.bat" />
|
</exec>
|
|
</target>
|
|
|
</project>
|
