vmassol     01/04/07 06:19:09

  Modified:    cactus/build build-servletapi.xml
  Log:
  removed the generation of the dependencies zip + dist target now suffix names with 
date instead of version + updates for new jakarta skin
  
  Revision  Changes    Path
  1.3       +23 -24    jakarta-commons-sandbox/cactus/build/build-servletapi.xml
  
  Index: build-servletapi.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-commons-sandbox/cactus/build/build-servletapi.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- build-servletapi.xml      2001/04/07 07:20:43     1.2
  +++ build-servletapi.xml      2001/04/07 13:19:08     1.3
  @@ -123,29 +123,6 @@
   
       <!-- 
          ========================================================================
  -         Full names of distributables
  -       ========================================================================
  -    -->
  -
  -    <!-- The Cactus jar file. This is the file that should be used at
  -         runtime by end users -->
  -    <property name="dist.jar.name" 
value="${dist.dir}/${jar.name}-${project.version}.jar"/>
  -
  -    <!-- The Cactus documentation for a given Servlet API in a zip :
  -         web site + javadoc + other READMEs. This file should be used by
  -         end users for getting help about Cactus -->
  -    <property name="dist.doc.name" 
value="${dist.dir}/${doc.name}-${project.version}.zip"/>
  -
  -    <!-- The Cactus javadocs for Servlet API 2.2 and 2.3.
  -         These files do not need to be redistributed to end-users. It is
  -         only needed to put the javadoc online to the Cactus web site. -->
  -    <property name="dist.javadoc.name" 
value="${dist.dir}/${javadoc.name}-${project.version}"/>
  -
  -    <!-- The Cactus sample zip for a given servlet API. -->
  -    <property name="dist.sample.name" 
value="${dist.dir}/${sample.name}-${project.version}.zip"/>
  -
  -    <!-- 
  -       ========================================================================
            Useful file patterns for targets
          ========================================================================
       -->
  @@ -203,6 +180,28 @@
           <filter token="servlet.jar" value="${servlet.jar}"/>
           <filter token="junit.jar" value="${junit.jar}"/>
           <filter token="servlet.api" value="${servlet.api}"/>
  +        <filter token="today" value="${TODAY}"/>
  +
  +        <!-- Full names of distributables. They are defined here because the
  +             properties need to have a valid ${DSTAMP} property set and the
  +             tstamp task need to be located in a target -->
  +    
  +        <!-- The Cactus jar file. This is the file that should be used at
  +             runtime by end users -->
  +        <property name="dist.jar.name" 
value="${dist.dir}/${jar.name}-${DSTAMP}.jar"/>
  +    
  +        <!-- The Cactus documentation for a given Servlet API in a zip :
  +             web site + javadoc + other READMEs. This file should be used by
  +             end users for getting help about Cactus -->
  +        <property name="dist.doc.name" 
value="${dist.dir}/${doc.name}-${DSTAMP}.zip"/>
  +    
  +        <!-- The Cactus javadocs for Servlet API 2.2 and 2.3.
  +             These files do not need to be redistributed to end-users. It is
  +             only needed to put the javadoc online to the Cactus web site. -->
  +        <property name="dist.javadoc.name" 
value="${dist.dir}/${javadoc.name}-${DSTAMP}"/>
  +    
  +        <!-- The Cactus sample zip for a given servlet API. -->
  +        <property name="dist.sample.name" 
value="${dist.dir}/${sample.name}-${DSTAMP}.zip"/>
   
       </target>
   
  @@ -424,7 +423,7 @@
   
           <!-- Generate the documentation web site -->
           <stylebook book="${xdoc.dir}/book.xml"
  -            skinDirectory="${skin.dir}/xml.apache.org"
  +            skinDirectory="${skin.dir}/jakarta.apache.org"
               targetDirectory="${out.doc.dir}">
   
               <classpath>
  
  
  

Reply via email to