build.xml 4.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384
  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="JMEBattleTank" default="jar" basedir=".">
  6. <description>Builds, tests, and runs the project .</description>
  7. <import file="nbproject/build-impl.xml"/>
  8. <!--
  9. There exist several targets which are by default empty and which can be
  10. used for execution of your tasks. These targets are usually executed
  11. before and after some main targets. They are:
  12. pre-init: called before initialization of project properties
  13. post-init: called after initialization of project properties
  14. pre-preprocess: called before text preprocessing of sources
  15. post-preprocess: called after text preprocessing of sources
  16. pre-compile: called before source compilation
  17. post-compile: called after source compilation
  18. pre-obfuscate: called before obfuscation
  19. post-obfuscate: called after obfuscation
  20. pre-preverify: called before preverification
  21. post-preverify: called after preverification
  22. pre-jar: called before jar building
  23. post-jar: called after jar building
  24. pre-build: called before final distribution building
  25. post-build: called after final distribution building
  26. pre-clean: called before cleaning build products
  27. post-clean: called after cleaning build products
  28. Example of pluging a my-special-task after the compilation could look like
  29. <target name="post-compile">
  30. <my-special-task>
  31. <fileset dir="${build.classes.dir}"/>
  32. </my-special-task>
  33. </target>
  34. For list of available properties check the imported
  35. nbproject/build-impl.xml file.
  36. Other way how to customize the build is by overriding existing main targets.
  37. The target of interest are:
  38. preprocess: preprocessing
  39. extract-libs: extraction of libraries and resources
  40. compile: compilation
  41. create-jad: construction of jad and jar manifest source
  42. obfuscate: obfuscation
  43. preverify: preverification
  44. jar: jar archive building
  45. run: execution
  46. debug: execution in debug mode
  47. build: building of the final distribution
  48. javadoc: javadoc generation
  49. Example of overriding the target for project execution could look like
  50. <target name="run" depends="init,jar">
  51. <my-special-exec jadfile="${dist.dir}/${dist.jad}"/>
  52. </target>
  53. Be careful about correct dependencies when overriding original target.
  54. Again, for list of available properties which you can use check the target
  55. you are overriding in nbproject/build-impl.xml file.
  56. A special target for-all-configs can be used to run some specific targets for
  57. all project configurations in a sequence. File nbproject/build-impl.xml
  58. already contains some "for-all" targets:
  59. jar-all
  60. javadoc-all
  61. clean-all
  62. Example of definition of target iterating over all project configurations:
  63. <target name="jar-all">
  64. <property name="target.to.call" value="jar"/>
  65. <antcall target="for-all-configs"/>
  66. </target>
  67. -->
  68. </project>