curcuru     00/08/21 12:30:07

  Modified:    .        README make.include
               src/org/apache/xalan/xslt XSLProcessorVersion.java
               xdocs/sources entities.ent
  Log:
  Update Xalan-J 1.x build number to 1.2D02 for upcoming release
  Update related Xerces-J reference to 1.1.3
  
  Revision  Changes    Path
  1.15      +2 -2      xml-xalan/README
  
  Index: README
  ===================================================================
  RCS file: /home/cvs/xml-xalan/README,v
  retrieving revision 1.14
  retrieving revision 1.15
  diff -u -r1.14 -r1.15
  --- README    2000/07/19 15:25:12     1.14
  +++ README    2000/08/21 19:29:58     1.15
  @@ -1,7 +1,7 @@
   README for xml-xalan project at xml.apache.org
   
  --- This Xalan build is 1.2D01. (i.e. the first Development drop to a 1.2 
build)
  -   It is compatible with Xerces 1.1.2
  +-- This Xalan build is 1.2D02. (i.e. the second Development drop to a 1.2 
build)
  +   It is compatible with Xerces 1.1.3
   
   -- IMPORTANT NOTES:
   
  
  
  
  1.13      +4 -1      xml-xalan/make.include
  
  Index: make.include
  ===================================================================
  RCS file: /home/cvs/xml-xalan/make.include,v
  retrieving revision 1.12
  retrieving revision 1.13
  diff -u -r1.12 -r1.13
  --- make.include      2000/07/19 15:25:13     1.12
  +++ make.include      2000/08/21 19:29:59     1.13
  @@ -1,3 +1,6 @@
  +# NOTE: use of makefiles is deprecated with Xalan-J build 1.2D02
  +# Please see the docs on using Ant's build.xml file instead
  +
   ###########################################################
   # Common variables and targets for XPath and xslt4j
   #
  @@ -30,7 +33,7 @@
   # Build-specific tools and flags definitions
   ###########################################################
   PRODUCT_NAME := xalan
  -VERSION      = _1_2_D01
  +VERSION      = _1_2_D02
   JARNAME      = $(PRODUCT_NAME)$(JARX)
   JARDISTNAME  = $(PRODUCT_NAME)-j$(VERSION)$(JARX)
   TARDISTNAME  = $(PRODUCT_NAME)-j$(VERSION)$(TARX)
  
  
  
  1.14      +2 -2      
xml-xalan/src/org/apache/xalan/xslt/XSLProcessorVersion.java
  
  Index: XSLProcessorVersion.java
  ===================================================================
  RCS file: 
/home/cvs/xml-xalan/src/org/apache/xalan/xslt/XSLProcessorVersion.java,v
  retrieving revision 1.13
  retrieving revision 1.14
  diff -u -r1.13 -r1.14
  --- XSLProcessorVersion.java  2000/07/19 15:25:17     1.13
  +++ XSLProcessorVersion.java  2000/08/21 19:30:03     1.14
  @@ -76,7 +76,7 @@
      * Version String like <CODE>"<B>Xalan</B>i v.r[.dd| <B>D</B>nn]"</CODE>.
      * <P>Semantics of the version string are identical to the Xerces 
project.</P>
      */
  -  public static String S_VERSION = "1.2D01";
  +  public static String S_VERSION = "1.2D02";
   
     /**
      * Constant name of product.
  @@ -140,5 +140,5 @@
      *          well as defect fixes. 'D' drops may not be as stable as
      *          the final releases.
      */
  -  public static int DEVELOPMENT = 1;
  +  public static int DEVELOPMENT = 2;
   }
  
  
  
  1.9       +3 -3      xml-xalan/xdocs/sources/entities.ent
  
  Index: entities.ent
  ===================================================================
  RCS file: /home/cvs/xml-xalan/xdocs/sources/entities.ent,v
  retrieving revision 1.8
  retrieving revision 1.9
  diff -u -r1.8 -r1.9
  --- entities.ent      2000/07/19 21:26:38     1.8
  +++ entities.ent      2000/08/21 19:30:06     1.9
  @@ -1,10 +1,10 @@
   <?xml encoding="US-ASCII"?>
   
   <!ENTITY xslt4j "Xalan-Java">
  -<!ENTITY xslt4j-dist "xalan-j_1_2_D01">
  -<!ENTITY xslt4j-current "&xslt4j; version 1.2.D01">
  +<!ENTITY xslt4j-dist "xalan-j_1_2_D02">
  +<!ENTITY xslt4j-current "&xslt4j; version 1.2.D02">
   <!ENTITY xml4j "Xerces-Java">
  -<!ENTITY xml4j-used "&xml4j; version 1.1.2">
  +<!ENTITY xml4j-used "&xml4j; version 1.1.3">
   <!ENTITY xslt4c "Xalan-C++">
   <!ENTITY xml4c "Xerces-C++">
   <!ENTITY download "The &xslt4j-current; download from xml.apache.org 
includes xerces.jar from &xml4j-used;.">
  
  
  

Reply via email to