Hi Josť,

Thanks for the report.† The issue you've encountered only shows up in unit tests -- it is actually a problem integrating beet with Spring's TestContext.† It is fixed in source control, and will be included in the forthcoming rc1 (if you're curious, the checkin that resolved the issue is here:† http://beet.git.sourceforge.net/git/gitweb.cgi?p=beet;a=commitdiff;h=68101059c70b5a5b6b32737771cfc3fb6dfffbfd).

I've also created an issue for the problem in case anyone else runs into this:† https://sourceforge.net/tracker/?func=detail&aid=2824858&group_id=258926&atid=1127321.

On the issue of 1.4 -- as soon as humanly possible :)† It's code-complete (assuming no other critical issues discovered in rc1) and is long overdue (I had hoped to be done a month ago).† I need to fix some problems with the release build and do a full regression test on the tutorial and example web app.

cheers
jason

2009/7/21 Rodriguez, Josť <Jose.Rodriguez@generali.ch>

Hi,

I'm having a look at Beet to monitor our applications and I may find a bug.
When I write a JUnit test with annotations, I have the following exception :