On Sat, Oct 25, 2008 at 1:24 AM, Mauro Talevi <[EMAIL PROTECTED]>wrote:
> You seem to have found the solution yourself - but to re-iterate: > > Maven 2 is very fussy about classloaders (most probably a reaction to Maven > 1 slack in this respect :-). So each scenario needs a Classloader to be > injected. This is in general no bad practice - one can always provide as > default the thread context classloades. I am not sure why a ClassLoader needs to be injected into my scenario. I am not using it in my scenario, nor am I passing it on to the superclass constructor. Is it possible for the ScenarioClassLoader to first look for a constructor which takes a CL and if not fall back to the default constructor? This might help people who don't want to configure a ClasspathScenarioDefiner etc which might need a CL. Thanks, Binil PS: The Maven plugin page does not yet have the configuration options.
