-
Apr 4th, 2012, 03:56 AM
#1
@Configurable causes ambiguous behaviour in unit tests.
From the spring documentation 7.8.1.1 Unit testing @Configurable objects, it is suggested that, if you weave classes at compile time, then warnings should be thrown when you create configurable classes in the unit tests.
However, when using maven to run a group of tests, then the configurable objects will start hunting for a context configuration.
Is this intended ? If not is it a spring or a maven prob.
Futher details : http://stackoverflow.com/questions/9...t-causes-error
Tags for this Thread
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules