<!-- 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="PizzaService" default="default" basedir="." xmlns:ear="http://www.netbeans.org/ns/j2ee-earproject/2">
- <description>Builds, tests, and runs the project PizzaService.</description>
+<project name="pizzaservice-core" default="default" basedir=".">
+ <description>Builds, tests, and runs the project pizzaservice-core.</description>
<import file="nbproject/build-impl.xml"/>
<!--
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-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
+ -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
- Example of pluging an obfuscator after the compilation could look like
+ (Targets beginning with '-' are not intended to be called on their own.)
- <target name="post-compile">
+ Example of inserting an obfuscator after compilation could look like this:
+
+ <target name="-post-compile">
<obfuscate>
<fileset dir="${build.classes.dir}"/>
</obfuscate>
nbproject/build-impl.xml file.
- Other way how to customize the build is by overriding existing main targets.
- The target of interest are:
+ Another way to customize the build is by overriding existing main targets.
+ The targets of interest are:
- do-dist: archive building
- run: execution of project
+ -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
- Example of overriding the target for project execution could look like
+ An example of overriding the target for project execution could look like this:
- <target name="run" depends="<PROJNAME>-impl.jar">
+ <target name="run" depends="pizzaservice-core-impl.jar">
<exec dir="bin" executable="launcher.exe">
<arg file="${dist.jar}"/>
</exec>
</target>
- 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
+ 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.
- -->
+ -->
</project>