Release Name: 2.3.0

Notes:
This package makes sourcing information from (parsing) configuration files
robust and easy!  It:
* Allows programmers to specify the type of data that should be loaded
  from a configuration file.  The toolkit automatically will validate
  the file's data against this specification when loading the file, ensuring
  that the specification always is obeyed and saving the programmer the
  tedious chore of writing validation code.
* Automagically generates parameter accessor methods (getters, setters, and
  predicates to test for presence), an equality operator, and a +to_s+ method
  from the configuration's specification.
* Allows programmers to create configuration files,
  easily and programatically.
* Provides a class that can load (parse) Ruby configuration files (allowing the
  full power of Ruby to be used within configuration files).
* Provides classes that can load from (parse) and dump to YAML and key-value
  configuration files.
* Provides classes that can load from and dump to Hashes.
* Provides a class that allows the contents of one configuration source to
  override the contents of another (this works with configuration files of any
  format or Hashes).
* Is very extensible, allowing the engine to be used with custom format
  configuration files and with custom data validation rules.


Changes:
=== 2.3.0 / 2009-06-09 
* The ConfigToolkit will print out a warning when it encounters an
  unknown parameter when loading a configuration file
  (ConfigToolkit::BaseConfig#load and ConfigToolkit::BaseConfig#load_group).
  This will make it easier to catch errors in configuration files.  Previously,
  such unknown parameters were ignored silently (thanks for the idea, Inaki).
* The ConfigToolkit now *itself* can be configured.
  ConfigToolkit::ConfigToolkitConfig configurations can be specified for a
  ConfigToolkit::BaseConfig child class or for an instance of a
  ConfigToolkit::BaseConfig child class.  The
  ConfigToolkit::ConfigToolkitConfig allows customization of the loading
  and dumping processes.  Right now, it supports modifying the ConfigToolkit's
  behavior upon encountering an unknown configuration parameter: the
  ConfigToolkit can ignore the parameter (the behavior in prior versions),
  warn about the parameter (the new default behavior), or raise a
  ConfigToolkit::Error about the parameter.  See README.txt for
  more details.