AspectWerkz 0.10 final has been released.

Download it.

This release is mainly a bug-fix release one month after 0.10.RC2, but brings lot of change compared to 0.9.

The following is the list of main differences compared to 0.9:
Read 0.10.RC2 release notes and 0.10.RC1 release notes.

• JIT compilation of JoinPoint for better performance
• Expressiveness and orthogonality with a more complete grammar
• Runtime weaving capabilities, the low layer for the upcoming hotdeployement feature
• Aspects can be any Java class and extend anything they like
• Retrieval of information about the system, adding and reading of parameters and metadata etc. is done through the CrossCuttingInfo class. An aspect or mixin that is interested in accessing this info should have a constructor that takes a CrossCuttingInfo instance as its only parameter. See the docs for details.
• Pluggable aspect container - The possibility to provide your own aspect container implementation is back. Useful if you need to control how your aspects are instantiated for example if you want that to be handled by an IoC container (Spring, PicoContainer etc.))

The following is the list of bug fix in 0.10 that were affecting 0.10.RC2:

• A thread safe issue has been fixed in the join point execution model.


• IBM JRE support has been fixed.


• Unix/Linux comamnd line scripts has been fixed (was missing bcel.jar).


• Exception throwned by method of weaved classes are not wrapped anymore. Exception throwned by mixin implementation are not wrapped anymore.


• JIT JoinPoint compilation is now thread safe.


• serialVersionUID computation fixed.


• Due to a lack of within expression support in the pointcut grammar (addressed in 1.0), the handler pointcut are very expensive to match. Those are deactivated by default. If your system uses those handler pointcuts, you have to add the -Daspectwerkz.handler.pointcut=true JVM option when starting up your JVM.

Note that the CVS has been migrated.
Check the instructions and update your tools.

Enjoy.