You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jcs-dev@jakarta.apache.org by hc...@apache.org on 2005/01/20 09:41:39 UTC

cvs commit: jakarta-turbine-jcs/auxiliary-builds/jdk15/yajcache/cache build-backup.xml build.xml

hchar       2005/01/20 00:41:39

  Modified:    auxiliary-builds/jdk15/yajcache/cache build.xml
  Added:       auxiliary-builds/jdk15/yajcache/cache build-backup.xml
  Log:
  no message
  
  Revision  Changes    Path
  1.2       +2 -0      jakarta-turbine-jcs/auxiliary-builds/jdk15/yajcache/cache/build.xml
  
  Index: build.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-turbine-jcs/auxiliary-builds/jdk15/yajcache/cache/build.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- build.xml	19 Jan 2005 11:01:15 -0000	1.1
  +++ build.xml	20 Jan 2005 08:41:39 -0000	1.2
  @@ -5,6 +5,7 @@
   <project name="cache" default="default" basedir=".">
       <description>Builds, tests, and runs the project cache.</description>
       <import file="nbproject/build-impl.xml"/>
  +    <import file="nbproject/profiler-build-impl.xml"/>
       <!--
   
       There exist several targets which are by default empty and which can be 
  @@ -67,3 +68,4 @@
   
       -->
   </project>
  +
  
  
  
  1.1                  jakarta-turbine-jcs/auxiliary-builds/jdk15/yajcache/cache/build-backup.xml
  
  Index: build-backup.xml
  ===================================================================
  <?xml version="1.0" encoding="UTF-8"?>
  <!-- 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.) -->
  <project name="cache" default="default" basedir=".">
      <description>Builds, tests, and runs the project cache.</description>
      <import file="nbproject/build-impl.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="cache-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. 
  
      -->
  </project>
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-jcs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-jcs-dev-help@jakarta.apache.org