Apr 4th, 2012, 03:56 AM
@Configurable causes ambiguous behaviour in unit tests.
From the spring documentation 220.127.116.11 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