<?xml version="1.0" encoding="UTF-8"?>
<!--

    DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.

    Copyright (c) 2018 Oracle and/or its affiliates. All rights reserved.

    The contents of this file are subject to the terms of either the GNU
    General Public License Version 2 only ("GPL") or the Common Development
    and Distribution License("CDDL") (collectively, the "License").  You
    may not use this file except in compliance with the License.  You can
    obtain a copy of the License at
    https://oss.oracle.com/licenses/CDDL+GPL-1.1
    or LICENSE.txt.  See the License for the specific
    language governing permissions and limitations under the License.

    When distributing the software, include this License Header Notice in each
    file and include the License file at LICENSE.txt.

    GPL Classpath Exception:
    Oracle designates this particular file as subject to the "Classpath"
    exception as provided by Oracle in the GPL Version 2 section of the License
    file that accompanied this code.

    Modifications:
    If applicable, add the following below the License Header, with the fields
    enclosed by brackets [] replaced by your own identifying information:
    "Portions Copyright [year] [name of copyright owner]"

    Contributor(s):
    If you wish your version of this file to be governed by only the CDDL or
    only the GPL Version 2, indicate your decision by adding "[Contributor]
    elects to include this software in this distribution under the [CDDL or GPL
    Version 2] license."  If you don't indicate a single choice of license, a
    recipient has the option to distribute your version of this file under
    either the CDDL, the GPL Version 2 or to extend the choice of license to
    its licensees as provided above.  However, if you add GPL Version 2 code
    and therefore, elected the GPL Version 2 license, then the option applies
    only if the new code is made subject to such option by the copyright
    holder.

-->

<!-- You may freely edit this file. See commented blocks below for -->
<!-- some examples of how to customize the build. -->
<!-- (If you delete it and reopen the project it will be recreated.) -->
<!-- By default, only the Clean and Build commands use this build script. -->
<!-- Commands such as Run, Debug, and Test only use this build script if -->
<!-- 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="pfl" default="default" basedir=".">
    <description>Builds, tests, and runs the project pfl.</description>
    <import file="nbproject/build-impl.xml"/>
    <import file="bundles.xml"/> 

    <!--

    There exist several targets which are by default empty and which can be 
    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-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

    (Targets beginning with '-' are not intended to be called on their own.)

    Example of inserting an obfuscator after compilation could look like this:

        <target name="-post-compile">
            <obfuscate>
                <fileset dir="${build.classes.dir}"/>
            </obfuscate>
        </target>

    For list of available properties check the imported 
    nbproject/build-impl.xml file. 


    Another way to customize the build is by overriding existing main targets.
    The targets of interest are: 

      -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-with-manifest:    JAR building (if you are using a manifest)
      -do-jar-without-manifest: JAR building (if you are not using a manifest)
      run:                      execution of project 
      -javadoc-build:           Javadoc generation
      test-report:              JUnit report generation

    An example of overriding the target for project execution could look like this:

        <target name="run" depends="pfl-impl.jar">
            <exec dir="bin" executable="launcher.exe">
                <arg file="${dist.jar}"/>
            </exec>
        </target>

    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. 

    -->
    <!--
    <target name="jars" depends="basic-jar,basic-tools-jar,tf-jar,
        tf-tools-jar,dynamic-jar,ff-jar"/>

    <target name="basic-jar">
        <jar jarfile="dist/basic.jar" duplicate="fail">
            <fileset dir="build/classes">
                <include name="org/glassfish/basic/**/*.class"/>
                <exclude name="org/glassfish/basic/tools/**/"/>
            </fileset>
        </jar>
    </target>

    <target name="basic-tools-jar">
        <jar jarfile="dist/basic-tools.jar" duplicate="fail">
            <fileset dir="build/classes">
                <include name="org/glassfish/basic/tools/**/"/>
            </fileset>
        </jar>
    </target>

    <target name="tf-jar">
        <jar jarfile="dist/tf.jar" duplicate="fail">
            <fileset dir="build/classes">
                <include name="org/glassfish/tf/**/*.class"/>
                <exclude name="org/glassfish/tf/tools/**/"/>
            </fileset>
        </jar>
    </target>

    <target name="tf-tools-jar">
        <jar jarfile="dist/tf-tools.jar" duplicate="fail">
            <fileset dir="build/classes">
                <include name="org/glassfish/tf/tools/**/"/>
            </fileset>
        </jar>
    </target>

    <target name="dynamic-jar">
        <jar jarfile="dist/dynamic.jar" duplicate="fail">
            <fileset dir="build/classes">
                <include name="org/glassfish/dynamic/**/*.class"/>
            </fileset>
        </jar>
    </target>

    <target name="ff-jar">
        <jar jarfile="dist/ff.jar" duplicate="fail">
            <fileset dir="build/classes">
                <include name="org/glassfish/ff/**/*.class"/>
            </fileset>
        </jar>
    </target>
    -->
</project>
