turbine-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From hoffm...@apache.org
Subject svn commit: r669802 - /turbine/core/branches/TURBINE_2_3_BRANCH/xdocs/changes.xml
Date Fri, 20 Jun 2008 06:53:17 GMT
Author: hoffmann
Date: Thu Jun 19 23:53:17 2008
New Revision: 669802

URL: http://svn.apache.org/viewvc?rev=669802&view=rev
Log:
changed the date to a real date

Modified:
    turbine/core/branches/TURBINE_2_3_BRANCH/xdocs/changes.xml

Modified: turbine/core/branches/TURBINE_2_3_BRANCH/xdocs/changes.xml
URL: http://svn.apache.org/viewvc/turbine/core/branches/TURBINE_2_3_BRANCH/xdocs/changes.xml?rev=669802&r1=669801&r2=669802&view=diff
==============================================================================
--- turbine/core/branches/TURBINE_2_3_BRANCH/xdocs/changes.xml (original)
+++ turbine/core/branches/TURBINE_2_3_BRANCH/xdocs/changes.xml Thu Jun 19 23:53:17 2008
@@ -27,7 +27,7 @@
 </properties>
 
 <body>
-  <release version="2.3.3-RC1" date="2008-05-??">
+  <release version="2.3.3-RC1" date="2008-06-12">
     <action type="update" dev="hoffmann">
       Preparing for the Release of Turbine 2.3.3
     </action>
@@ -64,14 +64,14 @@
       field types.
     </action>
     <action type="update" dev="tv">
-      Important change: The BaseValueParser now consistently returns null for 
+      Important change: The BaseValueParser now consistently returns null for
       all get-methods that return an Object, if the parameter name does not exist.
-      This changes the behaviour of getBigDecimal which used to return 0 in this 
+      This changes the behaviour of getBigDecimal which used to return 0 in this
       case.
     </action>
     <action type="update" dev="tv">
-      Initialize the locale of RunData, the ParameterParser and the CookieParser 
-      from the HttpServletRequest. Make RunData.setLocale propagate the locale 
+      Initialize the locale of RunData, the ParameterParser and the CookieParser
+      from the HttpServletRequest. Make RunData.setLocale propagate the locale
       setting to the parsers.
     </action>
     <action type="update" dev="tv">
@@ -80,7 +80,7 @@
     </action>
     <action type="add" dev="tv">
       Made ValueParser and BaseValueParser locale-aware. Note that the default
-      locale used is always the default value of the JVM which is different from 
+      locale used is always the default value of the JVM which is different from
       the previous behaviour where the locale used was sometimes Locale.US (for
       float, double and BigDecimal) and sometimes the JVM-default (for dates).
     </action>
@@ -171,7 +171,7 @@
     <action type="remove" dev="tv">
       Remove long deprecated classes.
       <ul>
-      	<li>org.apache.turbine.util.SequencedHashtable</li>
+        <li>org.apache.turbine.util.SequencedHashtable</li>
         <li>org.apache.turbine.util.StringStackBuffer</li>
         <li>org.apache.turbine.util.FileUtils</li>
         <li>org.apache.turbine.util.BufferCache</li>
@@ -184,8 +184,8 @@
         <li>org.apache.java.lang.*</li>
         <li>org.apache.java.security.*</li>
         <li>org.apache.turbine.util.db.*</li>
-   	    <li>org.apache.turbine.services.resources.TurbineResources</li>
-	    <li>org.apache.turbine.services.db.*</li>
+         <li>org.apache.turbine.services.resources.TurbineResources</li>
+      <li>org.apache.turbine.services.db.*</li>
       </ul>
     </action>
     <action type="add" dev="tv">
@@ -460,13 +460,13 @@
     <action type="update">
        Upgraded to commons-pool-1.1
     </action>
-  	 <action type="update">
-   	   HttpUtils.httpDateFormat had the year set as 'yyyyy', should be 'yyyy' therefore
-   	   setting expiry dates failed.
-  	 </action>
-  	 <action type="update">
-  	   TTWS60: HtmlPageAttributes setBackground sets the incorrect key name.
-  	 </action>
+     <action type="update">
+        HttpUtils.httpDateFormat had the year set as 'yyyyy', should be 'yyyy' therefore
+        setting expiry dates failed.
+     </action>
+     <action type="update">
+       TTWS60: HtmlPageAttributes setBackground sets the incorrect key name.
+     </action>
   </release>
 
 <release version="Turbine 2.3">
@@ -481,14 +481,14 @@
       use at least Maven 1.0b9, you will have to install it manually
       before you can recompile the source code.
     </action>
-    	<action type="update">
+      <action type="update">
       The IntakeService has been refactored, introducing two Abstract classes; the
       DefaultValidator and the NumberValidator. They both contain rules which are
       applicable to all Validator's and NumbeValidator's respectively. Unnecessary use
       was being made of (Old) NumberValidator which used BigDecimals, cleaned this up
       implementing concrete classes for all Number Types. Simplified definition of
       (number &amp; required) rules in Intake.xml.
-  	</action>
+    </action>
     <action type="update">
       The LoginUser action no longer checks to see if the user object is already
       in the session and returns if it is found.  The user will always be there
@@ -553,30 +553,30 @@
       commons-fileupload component.
     </action>
       <action type="update">
-	 Added ability to specify either the class TurbineResources.properties file
-	 or a new TurbineConfiguration.xml file.  TurbineConfiguration.xml allows
-	 Turbine to pull it's configuration values from multiple locations.  Please
-	 read the howto for more information.
-    </action>
-    <action type="update">
-	 Added a Howto describing using Hibernate with Turbine.  The actual code is
-	 currently not part of the Turbine distribution due to licensing issues, but is very
-	 easy to implement due to Turbine support of Avalon Components.
-    </action>
-    <action type="update">
-	 Changed TurbineUser so that when either permanent or temporary values are
-	 stored, if the required hashtable was missing, then it was created.  This
-	 happened in conjunction with the PassiveUserManager.  Additionally, the
-	 setTempStorage(Hashtable newTempStorage) did not actually assign the new
-	 Hashtable.  Cleaned up some of the code so the parallel permanent and temp
-	 data storage methods followed the same patterns.  Created a cactus testcase
-	 to test TurbineUser.
-    </action>
-    <action type="update">
-	 Changed scheduler so that if it is NOT enabled, then it doesn't attempt
-	 to connect to the database and retrieve jobs.  This prevents a spurious
-	 no data source error from showing up in the turbine logs on startup.  Added
-	 a cactus test to test the fix.
+   Added ability to specify either the class TurbineResources.properties file
+   or a new TurbineConfiguration.xml file.  TurbineConfiguration.xml allows
+   Turbine to pull it's configuration values from multiple locations.  Please
+   read the howto for more information.
+    </action>
+    <action type="update">
+   Added a Howto describing using Hibernate with Turbine.  The actual code is
+   currently not part of the Turbine distribution due to licensing issues, but is very
+   easy to implement due to Turbine support of Avalon Components.
+    </action>
+    <action type="update">
+   Changed TurbineUser so that when either permanent or temporary values are
+   stored, if the required hashtable was missing, then it was created.  This
+   happened in conjunction with the PassiveUserManager.  Additionally, the
+   setTempStorage(Hashtable newTempStorage) did not actually assign the new
+   Hashtable.  Cleaned up some of the code so the parallel permanent and temp
+   data storage methods followed the same patterns.  Created a cactus testcase
+   to test TurbineUser.
+    </action>
+    <action type="update">
+   Changed scheduler so that if it is NOT enabled, then it doesn't attempt
+   to connect to the database and retrieve jobs.  This prevents a spurious
+   no data source error from showing up in the turbine logs on startup.  Added
+   a cactus test to test the fix.
     </action>
     <action type="update">
       A new pull tool is available in the session scope called $sessionData.
@@ -661,9 +661,9 @@
            Configuration values can now be stored in XML, .properties, as well as JNDI Tree.
          </action>
          <action type="update">
-		   Configuration values can be overridden.  If you specify JNDI and the .xml, if a value
-		   is found in JNDI, then it is used.  Useful for overriding environment specific values
-		   like mail servers or whether Velocity templates are reloadable.
+       Configuration values can be overridden.  If you specify JNDI and the .xml, if a value
+       is found in JNDI, then it is used.  Useful for overriding environment specific values
+       like mail servers or whether Velocity templates are reloadable.
          </action>
            </action>
     <action type="update">



Mime
View raw message