Jrugged 2.0.0 has been released

6 views

Skip to first unread message

Moore, Jonathan

unread,

Mar 16, 2010, 1:20:45 PM3/16/10

to jrugg...@googlegroups.com, jrugge...@googlegroups.com, jrugged-...@googlegroups.com

Hi folks,

We've just released a new version of Jrugged; in addition to offering
some new features (like easy integration with the Spring Framework,
including Spring interceptors and JMX annotations), we've cleaned up
enough of the existing codebase that we felt this warranted a 2.X
release.

Latest release:
http://jrugged.googlecode.com/files/jrugged-core-2.0.0.jar
http://jrugged.googlecode.com/files/jrugged-aspects-2.0.0.jar
http://jrugged.googlecode.com/files/jrugged-spring-2.0.0.jar

You can also grab the source code for some working examples here:
http://jrugged.googlecode.com/files/jrugged-examples-2.0.0-sources.jar

While some method calls and parameters may have changed slightly, in
general, we didn't remove any functionality here, so you ought to be
able to relatively easily re-integrate with 2.0.0 if you are a 1.X user
already. Our hope is that the cleanup work that was done will leave us
in a sufficiently maintainable and flexible place that we'll be able to
maintain backwards compatibility for future releases. Please post to
jrugge...@googlegroups.com if you need assistance upgrading.

We'd also like to announce that the Javadocs for the latest release are
now available online (and are linked from the project home page on
Google Code).

http://jrugged.s3.amazonaws.com/jrugged-core-2.0.0/apidocs/index.html
http://jrugged.s3.amazonaws.com/jrugged-aspects-2.0.0/apidocs/index.html
http://jrugged.s3.amazonaws.com/jrugged-spring-2.0.0/apidocs/index.html

Finally, we are keeping a release ChangeLog online here:
http://code.google.com/p/jrugged/wiki/ChangeLog

The relevant excerpt for this release is:

Version 2.0.0 : 16 March 2010
* Added support for the Spring framework in the jrugged-spring
subproject.
* Refactored CircuitBreakers to use an external helper
FailureInterpreter class to determine whether a failure should cause
them to trip or not.
* Simplified the DefaultFailureInterpreter.
* Renamed some classes in jrugged-aspects to more closely align with
the naming of things in the jrugged-core library.
* PerformanceMonitors now record their MovingAverage updates inline
rather than spawning a background thread to do periodic sampling.
* Thorough Javadoc review and cleanup.