antonio     2004/06/26 18:14:17

  Modified:    .        status.xml
               lib      jars.xml
  Added:       lib/core commons-logging-1.0.4.jar
  Removed:     lib/optional commons-logging-1.0.4.jar
  Log:
  Move commons-logging-1.0.4.jar to lib/core as jcs.jar depends on it
  Bugzilla Report: 29369
  Reported by: Juan Jose Pablos
  
  Revision  Changes    Path
  1.374     +4 -1      cocoon-2.1/status.xml
  
  Index: status.xml
  ===================================================================
  RCS file: /home/cvs/cocoon-2.1/status.xml,v
  retrieving revision 1.373
  retrieving revision 1.374
  diff -u -r1.373 -r1.374
  --- status.xml        27 Jun 2004 00:44:35 -0000      1.373
  +++ status.xml        27 Jun 2004 01:14:17 -0000      1.374
  @@ -204,6 +204,9 @@
   
     <changes>
    <release version="@version@" date="@date@">
  +   <action dev="AG" type="fix" fixes-bug="29369" due-to="Juan Jose Pablos">
  +     Move commons-logging-1.0.4.jar to lib/core as jcs.jar depends on it
  +   </action>
      <action dev="AG" type="fix" fixes-bug="17924" due-to="Jorg Heymans">
        Apply patch: Cached resources don't have Expires-Header.
      </action>
  
  
  
  1.229     +2 -2      cocoon-2.1/lib/jars.xml
  
  Index: jars.xml
  ===================================================================
  RCS file: /home/cvs/cocoon-2.1/lib/jars.xml,v
  retrieving revision 1.228
  retrieving revision 1.229
  diff -u -r1.228 -r1.229
  --- jars.xml  18 Jun 2004 07:10:45 -0000      1.228
  +++ jars.xml  27 Jun 2004 01:14:17 -0000      1.229
  @@ -462,7 +462,7 @@
        The Logging package is an ultra-thin bridge between different logging 
libraries.
       </description>
       <used-by>Jakarta Commons HttpClient, Chaperon</used-by>
  -    <lib>optional/commons-logging-1.0.4.jar</lib>
  +    <lib>core/commons-logging-1.0.4.jar</lib>
       <homepage>http://jakarta.apache.org/commons/logging/</homepage>
     </file>
   
  
  
  
  1.1                  cocoon-2.1/lib/core/commons-logging-1.0.4.jar
  
        <<Binary file>>
  
  

Reply via email to