zapomenutý build.xml u EJB projektu
authorFrantišek Kučera <franta-hg@frantovo.cz>
Wed, 23 Jun 2010 15:43:43 +0200
changeset 1479d584f80e817
parent 146 61fb2c0fbcbc
child 148 784b3945c440
zapomenutý build.xml u EJB projektu
java/nekurak.net-ejb/build.xml
java/nekurak.net-rest/build.xml
java/nekurak.net-ws/build.xml
     1.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     1.2 +++ b/java/nekurak.net-ejb/build.xml	Wed Jun 23 15:43:43 2010 +0200
     1.3 @@ -0,0 +1,68 @@
     1.4 +<?xml version="1.0" encoding="UTF-8"?>
     1.5 +<!-- You may freely edit this file. See commented blocks below for -->
     1.6 +<!-- some examples of how to customize the build. -->
     1.7 +<!-- (If you delete it and reopen the project it will be recreated.) -->
     1.8 +<!-- By default, only the Clean and Build commands use this build script. -->
     1.9 +<!-- Commands such as Run, Debug, and Test only use this build script if -->
    1.10 +<!-- the Compile on Save feature is turned off for the project. -->
    1.11 +<!-- You can turn off the Compile on Save (or Deploy on Save) setting -->
    1.12 +<!-- in the project's Project Properties dialog box.-->
    1.13 +<project name="nekurak.net-ejb" default="default" basedir="." xmlns:ejbjarproject="http://www.netbeans.org/ns/j2ee-ejbjarproject/3">
    1.14 +    <description>Builds, tests, and runs the project nekurak.net-ejb.</description>
    1.15 +    <import file="nbproject/build-impl.xml"/>
    1.16 +    <!--
    1.17 +
    1.18 +    There exist several targets which are by default empty and which can be 
    1.19 +    used for execution of your tasks. These targets are usually executed 
    1.20 +    before and after some main targets. They are: 
    1.21 +
    1.22 +      -pre-init:                 called before initialization of project properties
    1.23 +      -post-init:                called after initialization of project properties
    1.24 +      -pre-compile:              called before javac compilation
    1.25 +      -post-compile:             called after javac compilation
    1.26 +      -pre-compile-single:       called before javac compilation of single file
    1.27 +      -post-compile-single:      called after javac compilation of single file
    1.28 +      -pre-dist:                 called before archive building
    1.29 +      -post-dist:                called after archive building
    1.30 +      -post-clean:               called after cleaning build products
    1.31 +      -pre-run-deploy:           called before deploying
    1.32 +      -post-run-deploy:          called after deploying
    1.33 +
    1.34 +    (Targets beginning with '-' are not intended to be called on their own.)
    1.35 +
    1.36 +    Example of pluging an obfuscator after the compilation could look like 
    1.37 +
    1.38 +        <target name="-post-compile">
    1.39 +            <obfuscate>
    1.40 +                <fileset dir="${build.classes.dir}"/>
    1.41 +            </obfuscate>
    1.42 +        </target>
    1.43 +
    1.44 +    For list of available properties check the imported 
    1.45 +    nbproject/build-impl.xml file. 
    1.46 +
    1.47 +
    1.48 +    Other way how to customize the build is by overriding existing main targets.
    1.49 +    The target of interest are: 
    1.50 +
    1.51 +      init-macrodef-javac:    defines macro for javac compilation
    1.52 +      init-macrodef-debug:    defines macro for class debugging
    1.53 +      do-dist:                archive building
    1.54 +      run:                    execution of project 
    1.55 +      javadoc-build:          javadoc generation 
    1.56 +
    1.57 +    Example of overriding the target for project execution could look like 
    1.58 +
    1.59 +        <target name="run" depends="<PROJNAME>-impl.jar">
    1.60 +            <exec dir="bin" executable="launcher.exe">
    1.61 +                <arg file="${dist.jar}"/>
    1.62 +            </exec>
    1.63 +        </target>
    1.64 +
    1.65 +    Notice that overridden target depends on jar target and not only on 
    1.66 +    compile target as regular run target does. Again, for list of available 
    1.67 +    properties which you can use check the target you are overriding in 
    1.68 +    nbproject/build-impl.xml file. 
    1.69 +
    1.70 +    -->
    1.71 +</project>
     2.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     2.2 +++ b/java/nekurak.net-rest/build.xml	Wed Jun 23 15:43:43 2010 +0200
     2.3 @@ -0,0 +1,71 @@
     2.4 +<?xml version="1.0" encoding="UTF-8"?>
     2.5 +<!-- You may freely edit this file. See commented blocks below for -->
     2.6 +<!-- some examples of how to customize the build. -->
     2.7 +<!-- (If you delete it and reopen the project it will be recreated.) -->
     2.8 +<!-- By default, only the Clean and Build commands use this build script. -->
     2.9 +<!-- Commands such as Run, Debug, and Test only use this build script if -->
    2.10 +<!-- the Compile on Save feature is turned off for the project. -->
    2.11 +<!-- You can turn off the Compile on Save (or Deploy on Save) setting -->
    2.12 +<!-- in the project's Project Properties dialog box.-->
    2.13 +<project name="nekurak.net-rest" default="default" basedir=".">
    2.14 +    <description>Builds, tests, and runs the project nekurak.net-rest.</description>
    2.15 +    <import file="nbproject/build-impl.xml"/>
    2.16 +    <!--
    2.17 +
    2.18 +    There exist several targets which are by default empty and which can be 
    2.19 +    used for execution of your tasks. These targets are usually executed 
    2.20 +    before and after some main targets. They are: 
    2.21 +
    2.22 +      -pre-init:                 called before initialization of project properties 
    2.23 +      -post-init:                called after initialization of project properties 
    2.24 +      -pre-compile:              called before javac compilation 
    2.25 +      -post-compile:             called after javac compilation 
    2.26 +      -pre-compile-single:       called before javac compilation of single file
    2.27 +      -post-compile-single:      called after javac compilation of single file
    2.28 +      -pre-compile-test:         called before javac compilation of JUnit tests
    2.29 +      -post-compile-test:        called after javac compilation of JUnit tests
    2.30 +      -pre-compile-test-single:  called before javac compilation of single JUnit test
    2.31 +      -post-compile-test-single: called after javac compilation of single JUunit test
    2.32 +      -pre-dist:                 called before archive building 
    2.33 +      -post-dist:                called after archive building 
    2.34 +      -post-clean:               called after cleaning build products 
    2.35 +      -pre-run-deploy:           called before deploying
    2.36 +      -post-run-deploy:          called after deploying
    2.37 +
    2.38 +    Example of pluging an obfuscator after the compilation could look like 
    2.39 +
    2.40 +        <target name="-post-compile">
    2.41 +            <obfuscate>
    2.42 +                <fileset dir="${build.classes.dir}"/>
    2.43 +            </obfuscate>
    2.44 +        </target>
    2.45 +
    2.46 +    For list of available properties check the imported 
    2.47 +    nbproject/build-impl.xml file. 
    2.48 +
    2.49 +
    2.50 +    Other way how to customize the build is by overriding existing main targets.
    2.51 +    The target of interest are: 
    2.52 +
    2.53 +      init-macrodef-javac:    defines macro for javac compilation
    2.54 +      init-macrodef-junit:   defines macro for junit execution
    2.55 +      init-macrodef-debug:    defines macro for class debugging
    2.56 +      do-dist:                archive building
    2.57 +      run:                    execution of project 
    2.58 +      javadoc-build:          javadoc generation 
    2.59 +
    2.60 +    Example of overriding the target for project execution could look like 
    2.61 +
    2.62 +        <target name="run" depends="<PROJNAME>-impl.jar">
    2.63 +            <exec dir="bin" executable="launcher.exe">
    2.64 +                <arg file="${dist.jar}"/>
    2.65 +            </exec>
    2.66 +        </target>
    2.67 +
    2.68 +    Notice that overridden target depends on jar target and not only on 
    2.69 +    compile target as regular run target does. Again, for list of available 
    2.70 +    properties which you can use check the target you are overriding in 
    2.71 +    nbproject/build-impl.xml file. 
    2.72 +
    2.73 +    -->
    2.74 +</project>
     3.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     3.2 +++ b/java/nekurak.net-ws/build.xml	Wed Jun 23 15:43:43 2010 +0200
     3.3 @@ -0,0 +1,72 @@
     3.4 +<?xml version="1.0" encoding="UTF-8"?>
     3.5 +<!-- You may freely edit this file. See commented blocks below for -->
     3.6 +<!-- some examples of how to customize the build. -->
     3.7 +<!-- (If you delete it and reopen the project it will be recreated.) -->
     3.8 +<!-- By default, only the Clean and Build commands use this build script. -->
     3.9 +<!-- Commands such as Run, Debug, and Test only use this build script if -->
    3.10 +<!-- the Compile on Save feature is turned off for the project. -->
    3.11 +<!-- You can turn off the Compile on Save (or Deploy on Save) setting -->
    3.12 +<!-- in the project's Project Properties dialog box.-->
    3.13 +<project name="nekurak.net-ws" default="default" basedir=".">
    3.14 +    <description>Builds, tests, and runs the project nekurak.net-ws.</description>
    3.15 +    <import file="nbproject/wsit-deploy.xml"/>
    3.16 +    <import file="nbproject/build-impl.xml"/>
    3.17 +    <!--
    3.18 +
    3.19 +    There exist several targets which are by default empty and which can be 
    3.20 +    used for execution of your tasks. These targets are usually executed 
    3.21 +    before and after some main targets. They are: 
    3.22 +
    3.23 +      -pre-init:                 called before initialization of project properties 
    3.24 +      -post-init:                called after initialization of project properties 
    3.25 +      -pre-compile:              called before javac compilation 
    3.26 +      -post-compile:             called after javac compilation 
    3.27 +      -pre-compile-single:       called before javac compilation of single file
    3.28 +      -post-compile-single:      called after javac compilation of single file
    3.29 +      -pre-compile-test:         called before javac compilation of JUnit tests
    3.30 +      -post-compile-test:        called after javac compilation of JUnit tests
    3.31 +      -pre-compile-test-single:  called before javac compilation of single JUnit test
    3.32 +      -post-compile-test-single: called after javac compilation of single JUunit test
    3.33 +      -pre-dist:                 called before archive building 
    3.34 +      -post-dist:                called after archive building 
    3.35 +      -post-clean:               called after cleaning build products 
    3.36 +      -pre-run-deploy:           called before deploying
    3.37 +      -post-run-deploy:          called after deploying
    3.38 +
    3.39 +    Example of pluging an obfuscator after the compilation could look like 
    3.40 +
    3.41 +        <target name="-post-compile">
    3.42 +            <obfuscate>
    3.43 +                <fileset dir="${build.classes.dir}"/>
    3.44 +            </obfuscate>
    3.45 +        </target>
    3.46 +
    3.47 +    For list of available properties check the imported 
    3.48 +    nbproject/build-impl.xml file. 
    3.49 +
    3.50 +
    3.51 +    Other way how to customize the build is by overriding existing main targets.
    3.52 +    The target of interest are: 
    3.53 +
    3.54 +      init-macrodef-javac:    defines macro for javac compilation
    3.55 +      init-macrodef-junit:   defines macro for junit execution
    3.56 +      init-macrodef-debug:    defines macro for class debugging
    3.57 +      do-dist:                archive building
    3.58 +      run:                    execution of project 
    3.59 +      javadoc-build:          javadoc generation 
    3.60 +
    3.61 +    Example of overriding the target for project execution could look like 
    3.62 +
    3.63 +        <target name="run" depends="<PROJNAME>-impl.jar">
    3.64 +            <exec dir="bin" executable="launcher.exe">
    3.65 +                <arg file="${dist.jar}"/>
    3.66 +            </exec>
    3.67 +        </target>
    3.68 +
    3.69 +    Notice that overridden target depends on jar target and not only on 
    3.70 +    compile target as regular run target does. Again, for list of available 
    3.71 +    properties which you can use check the target you are overriding in 
    3.72 +    nbproject/build-impl.xml file. 
    3.73 +
    3.74 +    -->
    3.75 +</project>