Announcing version 3.0.0 of the JRugged Library

[joseph_...@comcast.com]

A new version of JRugged is now available for download and includes a
series of really great improvements to the library. Please check out
the new version at the project home located here: http://code.google.com/p/jrugged/.
The changes are summarized below.

ENJOY,

The JRugged Team.

19 September 2011: Version 3.0.0 of the JRugged Library released!

Fixed issue #35 : Cleaned up and added Java Doc where it was missing

Fixed issue #37 : Fixed an NPE in PerformanceMonitor

Fixed issue #38 : NPE from DefaultFailureInterpreter (synchronization
issue)

Enhancement issue #40 : Allows a CircuitBreaker to start/initialize
in a hard trip state.

Enhancement issue #41 : Provide an exception mapper patter for the
ConstantFlowRegulator

Fixed issue #42 : Compilation error due to log4j dependency

Enhancement issue #43 : The annotations available in the aspects
package can now make use of the beans for PerformanceMonitors
andCircuitBreakers allowing for a much cleaner implementation. The
annotations are now much more useful and robust.

Enhancement issue #44 : RolledUpStatus was improved to allow a more
concise status reporting. The naming of the classes associated with
the status have changed as well - to improve the readability and
understandability of the code base.

Enhancement issue #45 : Changed the pom's to include a more recent
version of Spring (3.0.5)

Enhancement issue #46 : Added a way in the spring integration to
automatically 'discover' those classes with the annotations included
in the aspects package to auto-publish their JMX information if there
is a JMX server already registered in the spring config.


Many thanks to walter_eggert at comcast dot com, coby_young at comcast
dot com, raghushankar_ramalingam at comcast dot com and
michajlo_matijkiw at comcast dot com (Mishu) who contributed to this
next great release of the JRugged Library.