--- /dev/null
+<?xml version="1.0" encoding="UTF-8"?>\r
+<!-- You may freely edit this file. See commented blocks below for -->\r
+<!-- some examples of how to customize the build. -->\r
+<!-- (If you delete it and reopen the project it will be recreated.) -->\r
+<!-- By default, only the Clean and Build commands use this build script. -->\r
+<!-- Commands such as Run, Debug, and Test only use this build script if -->\r
+<!-- the Compile on Save feature is turned off for the project. -->\r
+<!-- You can turn off the Compile on Save (or Deploy on Save) setting -->\r
+<!-- in the project's Project Properties dialog box.-->\r
+<project name="MMDLoaderJME3-lib" default="default" basedir=".">\r
+ <description>Builds, tests, and runs the project MMDLoaderJME3-lib.</description>\r
+ <import file="nbproject/build-impl.xml"/>\r
+ <!--\r
+\r
+ There exist several targets which are by default empty and which can be \r
+ used for execution of your tasks. These targets are usually executed \r
+ before and after some main targets. They are: \r
+\r
+ -pre-init: called before initialization of project properties\r
+ -post-init: called after initialization of project properties\r
+ -pre-compile: called before javac compilation\r
+ -post-compile: called after javac compilation\r
+ -pre-compile-single: called before javac compilation of single file\r
+ -post-compile-single: called after javac compilation of single file\r
+ -pre-compile-test: called before javac compilation of JUnit tests\r
+ -post-compile-test: called after javac compilation of JUnit tests\r
+ -pre-compile-test-single: called before javac compilation of single JUnit test\r
+ -post-compile-test-single: called after javac compilation of single JUunit test\r
+ -pre-jar: called before JAR building\r
+ -post-jar: called after JAR building\r
+ -post-clean: called after cleaning build products\r
+\r
+ (Targets beginning with '-' are not intended to be called on their own.)\r
+\r
+ Example of inserting an obfuscator after compilation could look like this:\r
+\r
+ <target name="-post-compile">\r
+ <obfuscate>\r
+ <fileset dir="${build.classes.dir}"/>\r
+ </obfuscate>\r
+ </target>\r
+\r
+ For list of available properties check the imported \r
+ nbproject/build-impl.xml file. \r
+\r
+\r
+ Another way to customize the build is by overriding existing main targets.\r
+ The targets of interest are: \r
+\r
+ -init-macrodef-javac: defines macro for javac compilation\r
+ -init-macrodef-junit: defines macro for junit execution\r
+ -init-macrodef-debug: defines macro for class debugging\r
+ -init-macrodef-java: defines macro for class execution\r
+ -do-jar-with-manifest: JAR building (if you are using a manifest)\r
+ -do-jar-without-manifest: JAR building (if you are not using a manifest)\r
+ run: execution of project \r
+ -javadoc-build: Javadoc generation\r
+ test-report: JUnit report generation\r
+\r
+ An example of overriding the target for project execution could look like this:\r
+\r
+ <target name="run" depends="MMDLoaderJME3-lib-impl.jar">\r
+ <exec dir="bin" executable="launcher.exe">\r
+ <arg file="${dist.jar}"/>\r
+ </exec>\r
+ </target>\r
+\r
+ Notice that the overridden target depends on the jar target and not only on \r
+ the compile target as the regular run target does. Again, for a list of available \r
+ properties which you can use, check the target you are overriding in the\r
+ nbproject/build-impl.xml file. \r
+\r
+ -->\r
++ <target name="src-jar" depends="init">\r
++ <jar basedir="src" jarfile="${dist.dir}/MMDLoaderJME3-source.jar"/>\r
++ </target>\r
++ <target name="javadoc-jar" depends="javadoc">\r
++ <jar basedir="${dist.dir}/javadoc" jarfile="${dist.dir}/MMDLoaderJME3-javadoc.jar"/>\r
++ </target>\r
+</project>\r
OSDN Git Service
