Actually, it was not even a problem with @Monitor, just a case of out of sync jars. A mvn -o clean on kernel (after fixing a number of test case problems created by my changes) got rid of the problem.
On 10/27/06, Jim Marino <[EMAIL PROTECTED]> wrote:
On Oct 27, 2006, at 7:08 AM, Jeremy Boynes wrote: > On Oct 27, 2006, at 6:53 AM, Jim Marino wrote: > >> It looks as if you have an @Monitor declared twice in the >> hierarchy for the component named "java.componentBuilder". It >> could be on a field, setter or constructor. We should probably >> allow multiple monitors to be injected in a class hierarchy. Can >> you take a look and see if that is the case and then we can figure >> out what we want to do to fix it? > > Is this a problem with @Monitor or annotations in general? Just @Monitor > -- > Jeremy
