SQL: změny v databázovém schématu (role, uživatelé, rozšíření… zapomenuté změny).
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 <!-- By default, only the Clean and Build commands use this build script. -->
6 <!-- Commands such as Run, Debug, and Test only use this build script if -->
7 <!-- the Compile on Save feature is turned off for the project. -->
8 <!-- You can turn off the Compile on Save (or Deploy on Save) setting -->
9 <!-- in the project's Project Properties dialog box.-->
10 <project name="nekurak.net-ear" default="default" basedir="." xmlns:ear="http://www.netbeans.org/ns/j2ee-earproject/2">
11 <description>Builds, tests, and runs the project nekurak.net-ear.</description>
12 <import file="nbproject/build-impl.xml"/>
15 There exist several targets which are by default empty and which can be
16 used for execution of your tasks. These targets are usually executed
17 before and after some main targets. They are:
19 pre-init: called before initialization of project properties
20 post-init: called after initialization of project properties
21 pre-compile: called before javac compilation
22 post-compile: called after javac compilation
23 pre-dist: called before archive building
24 post-dist: called after archive building
25 post-clean: called after cleaning build products
26 pre-run-deploy: called before deploying
27 post-run-deploy: called after deploying
29 Example of pluging an obfuscator after the compilation could look like
31 <target name="post-compile">
33 <fileset dir="${build.classes.dir}"/>
37 For list of available properties check the imported
38 nbproject/build-impl.xml file.
41 Other way how to customize the build is by overriding existing main targets.
42 The target of interest are:
44 do-dist: archive building
45 run: execution of project
47 Example of overriding the target for project execution could look like
49 <target name="run" depends="<PROJNAME>-impl.jar">
50 <exec dir="bin" executable="launcher.exe">
51 <arg file="${dist.jar}"/>
55 Notice that overridden target depends on jar target and not only on
56 compile target as regular run target does. Again, for list of available
57 properties which you can use check the target you are overriding in
58 nbproject/build-impl.xml file.