[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [aspectj-users] FATAL-AspectJWeaverLogger - trouble in: FOUND REASON
- From: Barry Kaplan <groups1@xxxxxxxxxxx>
- Date: Wed, 10 May 2006 08:18:08 -0400
- Delivered-to: email@example.com
- User-agent: Thunderbird 126.96.36.199 (Windows/20060308)
Barry Kaplan wrote:
Hmm, I don't see why spring decided to weave that class. But I do need
the aspect deployed.
I found out what is going on! In one of my unit tests (which gets run
along with the integration tests with LTW enabled) is doing:
private IMocksControl control = createStrictControl();
private DisableableAnnotationBeanConfigurerAspect mockDisabler =
This is what is creating the CGLIB version of the aspect.
The following seems to prevent the weaving of this particular mock subclass:
I would love to ensure that no EasyMock CGLIB'ed generated classes get
weaved by using "*$$EnhancerByCGLIB$$*", but I have lots other classes
generated by CGLIB that I /do/ want weaved (eg, Hibernate classes).
Maybe I will just have to live without a single "test-all" and run tests
unit and integration tests separately.