Author: oheger
Date: Tue Feb 13 13:20:43 2007
New Revision: 507232

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

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

Modified: jakarta/commons/proper/configuration/trunk/RELEASE-NOTES.txt
URL: 
http://svn.apache.org/viewvc/jakarta/commons/proper/configuration/trunk/RELEASE-NOTES.txt?view=diff&rev=507232&r1=507231&r2=507232
==============================================================================
--- jakarta/commons/proper/configuration/trunk/RELEASE-NOTES.txt (original)
+++ jakarta/commons/proper/configuration/trunk/RELEASE-NOTES.txt Tue Feb 13 
13:20:43 2007
@@ -53,14 +53,6 @@
   variable interpolation. So it is possible to refer to a variable in one
   (sub) configuration that is defined in another configuration.
 
-* [CONFIGURATION-234]
-  DefaultConfigurationBuilder now internally uses the standard expression
-  engine for hierarchical configurations. So the dependency to Commons JXPath
-  is no more needed when this class is used. Note that this change has some
-  impact on exist ing code that manually sets properties before the combined
-  configuration is created; this code must now be adapted to the changed
-  syntax of property keys.
-
 * [CONFIGURATION-235]
   Interpolation of non string values did not work when SubsetConfiguration
   was involved. This has now been fixed.
@@ -78,13 +70,6 @@
   CompositeConfiguration.clearProperty() now generates the correct update
   events.
 
-* [CONFIGURATION-242]
-  The configuration returned by HierarchicalConfiguration.subset() performed
-  variable interpolation only in the keys that belong to the subset. Now the
-  parent configuration is searched, too, to resolve the value of the
-  referenced property. This is consistent with the way SubnodeConfiguration
-  works.
-
 * [CONFIGURATION-244]
   The number of dependencies needed for DefaultConfigurationBuilder was reduced
   by letting some of the default configuration providers resolve their classes
@@ -95,7 +80,7 @@
   used version 2.0.2 is reported to be bogus.
 
 * [CONFIGURATION-252]
-  ConfigurationUtils.getFile() now always checks first´whether the passed in
+  ConfigurationUtils.getFile() now always checks first whether the passed in
   file name is absolute. If it is, this file will be returned. This prevents
   that on Unix under certain circumstances absolute file names are interpreted
   as relative ones.
@@ -122,6 +107,10 @@
   HierarchicalConfiguration and some of its sub classes now define a copy
   constructor.
 
+* [CONFIGURATUON-237]
+  With ManagedReloadingStrategy a new reloading strategy for file-based
+  configurations was added that can be triggered through JMX.
+
 * [CONFIGURATION-243]
   Configuration declarations in the configuration definition file for
   DefaultConfigurationBuilder that are marked as optional now support a new
@@ -139,6 +128,29 @@
   error listener at the passed in configuration that generates a runtime
   exception when an error event is received.
 
+CHANGES THAT MIGHT IMPACT EXISTING CODE:
+========================================
+
+* [CONFIGURATION-234]
+  DefaultConfigurationBuilder now internally uses the standard expression
+  engine for hierarchical configurations. So the dependency to Commons JXPath
+  is no more needed when this class is used. Note that this change has some
+  impact on exist ing code that manually sets properties before the combined
+  configuration is created; this code must now be adapted to the changed
+  syntax of property keys.
+
+* [CONFIGURATION-242]
+  The configuration returned by HierarchicalConfiguration.subset() performed
+  variable interpolation only in the keys that belong to the subset. Now the
+  parent configuration is searched, too, to resolve the value of the
+  referenced property. This is consistent with the way SubnodeConfiguration
+  works, but it slightly changes the behavior of interpolation for
+  configurations that are loaded by DefaultConfigurationBuilder and are
+  stored in the resulting CombinedConfiguration under a prefix. If a
+  subset is fetched for this prefix, in version 1.3 variables could be
+  resolved that belong to the same subset. This does not work any more in
+  version 1.4
+
 OTHER CHANGES
 =============
 
@@ -152,4 +164,4 @@
 * The dependencies to Commons Collections and Commons Digester are updated to
   use the recent available version. However older versions will still work.
 
-* A pom for maven 2 was added.
\ No newline at end of file
+* A pom for maven 2 was added.



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to