Hi Marcin, thanks again for the fast response on the Java 6 compatibility issue.
I've identified the further problem I was having. My test involves a @Subject which is a Spy, and I stub a method which is called internally which would otherwise throw an exception (when run out-of-container). When the subject is managed by your extension, the stubbing is ignored, the original method is invoked and I get an exception.
I'd be very grateful for any thoughts on why this is and whether the extension can be modified to allow stubbing/partial-mocking on a Spy, or whether the way it works is just not compatible.
Hi! It's incompatible with my approach since I'm instantiating the class and either by constructor, setter or a property try to inject your collaborator to a subject. If you're creating a spy then I'm just ignoring this and normally instantiating an object. I would have to for example check if you haven't already created a spy and if that is the case I would have to omit the object instantation.
But to tell you the truth I think I know how to solve this ;) I'll try to release a version today