Changeset 64 in tmcsimulator for trunk/IDE_metadata/NetBeans/TMCSim/build.xml


Ignore:
Timestamp:
03/16/2017 07:28:12 AM (9 years ago)
Author:
jdalbey
Message:

Renamed to ClockClient?, added build target for it.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/IDE_metadata/NetBeans/TMCSim/build.xml

    r59 r64  
    8989<!-- 
    9090                ================= 
    91                 LOC counter  
     91                LOC counter 
    9292                ================= 
    9393--> 
     
    9696              classpath="${workdir}/lib/JavaLOC.jar"> 
    9797               <arg line="-r -d ${workdir}/src"/> 
    98         </java>     
    99 </target>     
     98        </java> 
     99</target> 
    100100<!-- 
    101101                ================= 
     
    143143                ================= 
    144144--> 
    145 <target description="Build separate jar files for each component of the TMC system."  
     145<target description="Build separate jar files for each component of the TMC system." 
    146146        name="package-jars" depends="jar"> 
    147147 
     
    211211        </manifest> 
    212212      </jar> 
    213       <!-- Remove the following line when we get CADClient to run  
     213      <!-- Remove the following line when we get CADClient to run 
    214214      <delete file="${deploy.dir}/CADClient.jar"/>--> 
    215        
     215 
     216      <!--                   *** Build Clock Client Only Jar ***         --> 
     217      <jar destfile="${deploy.dir}/ClockClient.jar" 
     218       basedir="${build.dir}/classes" 
     219       includes="tmcsim/client/ClockClient*.class, tmcsim/client/ClockView.class, 
     220        tmcsim/interfaces/**, tmcsim/cadmodels/**, tmcsim/common/**, tmcsim/client/**"> 
     221      <zipgroupfileset dir="dist/lib" includes="xercesImpl.jar"/> 
     222        <manifest> 
     223            <attribute name="Main-Class" value="tmcsim.client.ClockClient"/> 
     224            <attribute name="Implementation-Version" value="${TODAY}"/> 
     225        </manifest> 
     226      </jar> 
     227 
    216228      <!--                   *** Build Paramics Communicator Only Jar ***         --> 
    217229      <jar destfile="${deploy.dir}/ParamicsCommunicator.jar" 
     
    227239</target> 
    228240 
    229 <target description="Build separate jar files for each component of the TMC system."  
     241<target description="Build separate jar files for each component of the TMC system." 
    230242        name="ZipForInstall" depends="package-jars"> 
    231243    <!-- Notes:    Create a zip file with jars and all external resources for distributing 
     
    240252    <!-- 
    241253 
    242     There exist several targets which are by default empty and which can be  
    243     used for execution of your tasks. These targets are usually executed  
    244     before and after some main targets. They are:  
     254    There exist several targets which are by default empty and which can be 
     255    used for execution of your tasks. These targets are usually executed 
     256    before and after some main targets. They are: 
    245257 
    246258      -pre-init:                 called before initialization of project properties 
     
    268280        </target> 
    269281 
    270     For list of available properties check the imported  
    271     nbproject/build-impl.xml file.  
     282    For list of available properties check the imported 
     283    nbproject/build-impl.xml file. 
    272284 
    273285 
    274286    Another way to customize the build is by overriding existing main targets. 
    275     The targets of interest are:  
     287    The targets of interest are: 
    276288 
    277289      -init-macrodef-javac:     defines macro for javac compilation 
     
    281293      -do-jar-with-manifest:    JAR building (if you are using a manifest) 
    282294      -do-jar-without-manifest: JAR building (if you are not using a manifest) 
    283       run:                      execution of project  
     295      run:                      execution of project 
    284296      -javadoc-build:           Javadoc generation 
    285297      test-report:              JUnit report generation 
     
    293305        </target> 
    294306 
    295     Notice that the overridden target depends on the jar target and not only on  
    296     the compile target as the regular run target does. Again, for a list of available  
     307    Notice that the overridden target depends on the jar target and not only on 
     308    the compile target as the regular run target does. Again, for a list of available 
    297309    properties which you can use, check the target you are overriding in the 
    298     nbproject/build-impl.xml file.  
     310    nbproject/build-impl.xml file. 
    299311 
    300312    --> 
Note: See TracChangeset for help on using the changeset viewer.