commons-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ohe...@apache.org
Subject svn commit: r1368239 - /commons/proper/configuration/trunk/RELEASE-NOTES.txt
Date Wed, 01 Aug 2012 20:25:29 GMT
Author: oheger
Date: Wed Aug  1 20:25:29 2012
New Revision: 1368239

URL: http://svn.apache.org/viewvc?rev=1368239&view=rev
Log:
Updated release notes.

Modified:
    commons/proper/configuration/trunk/RELEASE-NOTES.txt

Modified: commons/proper/configuration/trunk/RELEASE-NOTES.txt
URL: http://svn.apache.org/viewvc/commons/proper/configuration/trunk/RELEASE-NOTES.txt?rev=1368239&r1=1368238&r2=1368239&view=diff
==============================================================================
--- commons/proper/configuration/trunk/RELEASE-NOTES.txt (original)
+++ commons/proper/configuration/trunk/RELEASE-NOTES.txt Wed Aug  1 20:25:29 2012
@@ -1,7 +1,7 @@
 $Id$
 
                            Commons Configuration Package
-                               Version 1.8
+                               Version 1.9
                                Release Notes
 
 
@@ -14,64 +14,49 @@ The Commons Configuration software libra
 interface which enables an application to read configuration data from a variety
 of sources.
 
-The main focus of the 1.8 release is support for Java 1.5; this is now the
-minimum required Java version. The API has been adapted to new language
-features - mainly generics - where it makes sense. This could be achieved in a
-binary compatible way; Commons Configuration 1.8 is fully binary compatible to
-the previous version.
-
-Although Commons Configuration 1.8 targets Java 1.5, it was not possible to
-update the dependency to Commons Lang to the new 3.x version. This is due to
-the fact that the public API of Configuration contains some classes of
-Commons Lang. Thus changing the dependency would mean breaking compatibility.
-Therefore, the update of the Commons Lang dependency can only take place in the
-next major release. In the mean time, if you want to use new features provided
-by Commons Lang 3.x, you have to add both versions of the library to the
-classpath. This will not cause any problems because in version 3.x the
-package names of Commons Lang have changed, so the classes can co-exist.
+The 1.9 release contains a couple of minor bug fixes and improvements. There
+are no important new features. The idea is to release the current changes which
+have been applied to the 1.x branch, so that we can start with new development
+on an improved (and partly binary incompatible) 2.0 version.
 
-Following is a complete list of all changes in the new 1.8 release:
+As there are small changes only, Commons Configuration 1.8 is fully binary
+compatible to the previous version. The minimum required Java version is 1.5.
 
-BUG FIXES IN 1.8
+Following is a complete list of all changes in the new 1.9 release:
+
+BUG FIXES IN 1.9
 ================
-* [CONFIGURATION-476]
-  Fixed possible ClassCastExceptions in CompositeConfiguration related to
-  special in-memory configurations.
+* [CONFIGURATION-495]
+  List properties can now be set correctly on a HierarchicalConfiguration if
+  delimiter parsing is disabled.
+
+* [CONFIGURATION-487]
+  DataConfiguration.get() now also works with String properties and if no data
+  type conversion is required.
+
+* [CONFIGURATION-481]
+  Variable substitution in configuration sources declared in a definition file
+  for DefaultConfigurationBuilder now works across multiple sources.
+
+ * [CONFIGURATION-477]
+   PropertyListConfiguration now can deal with C-style comments in plist
+   configuration files. Both block and single-line comments are supported.
 
-IMPROVEMENTS AND NEW FEATURES IN 1.7
+IMPROVEMENTS AND NEW FEATURES IN 1.9
 ====================================
-* [CONFIGURATION-475]
-  Class ConfigurationKey was deprecated in favor of DefaultConfigurationKey.
-
-* [CONFIGURATION-474]
-  Implemented delimiter parsing in HierarchicalINIConfiguration to be
-  consistent with other Configuration implementations. Note that this can
-  impact existing code. To switch back to the old behavior, call
-  setDelimiterParsingDisabled(true) before loading the configuration.
-
-* [CONFIGURATION-471]
-  CompositeConfiguration now provides better support for child configurations
-  that are used as in-memory configuration.
-
-* [CONFIGURATION-466]
-  Binary literals are now supported (i.e Ob11010001).
-
-* [CONFIGURATION-465]
-  Updated the dependency to Commons Jexl to version 2.1.1. This version
-  provides correct OSGi manifest headers.
-
-* [CONFIGURATION-463]
-  Improved documentation of AbstractFileConfiguration related to load()
-  methods and their impact on the base path.
+* [CONFIGURATION-501]
+  XMLPropertyListConfiguration no longer swallows exception caused by invalid
+  date properties. Now a warning message is logged.
+
+* [CONFIGURATION-483]
+  DatabaseConfiguration now always closes the result set.
+
+* [CONFIGURATION-482]
+  The Import-Package section in the OSGi manifest now uses the
+  resolution:=optional directive for optional dependencies.
 
 OTHER CHANGES
 =============
-* Commons Configuration now requires Java 5 or later. The API has been slightly
-  adapted to new language features.
-
-* [CONFIGURATION-470]
-  Classes generated by JavaCC are now created dynamically during the build
-  process.
+* The dependency to Commons Codec has been updated to the most recent 1.6
+  version. The older version still works.
 
-* [CONFIGURATION-461]
-  The project now uses standard Maven directory layout.



Mime
View raw message