The initial problem was to @Inject user's implementation of client-api (some dependency) in MOJO.
No problem if user implements our interfaces in a dependency for surefire plugin - this may modify RunOrder feature for instance. Should work... I am sure that some users will say that they have 1000 modules, the dependencies cannot be configured like plugins, and each of them needs different implementation of our interfaces and thus plenty of new dependencies. The extensions might be a partial solution, however I don't think surefire has an ambition to modify lifecycle, but we will be in the same point where we are now because of new JIRA issues will come to make new configuration entries in the extension plugin. We can do the same what @Lennart mentioned with EnforcerRule <coffeCooker implementation="your.coffee.ExtensionCooker"/> , but I know that stephenc mentioned in other post that this is not ideal extension style. Some users may come with a wish to have implementation of the interfaces in test classes src/test/java/**/instrumentation/**/*.java, without creating new dependency module and extension plugin. Not creating new modules and extension plugins makes their life easier. -- View this message in context: http://maven.40175.n5.nabble.com/Plugable-Softcoded-Customized-Maven-Plugins-tp5823365p5823781.html Sent from the Maven Developers mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
