> > I've always been thinking we'd pick such stuff up from "somewhere". > For surefire I've always figured test scope.
Wouldn't it be better to get it from the classpath of the mojo execution? i.e. it should be added as a dep to the plugin declaration. /Anders > A more general solution > would perhaps be to permit an entire module in a multi-module build to > contain extension mechanisms; so such a module could add dependencies > to the public api of the plugin and thereby gain access to a set of > extension points. > > Kristian > > > 2015-01-14 11:58 GMT+01:00 Tibor Digana <tibordig...@apache.org>: > > Hi Kristian, Igor, > > > > I think i have found the way to inject custom objects into plugin > execution > > without SPI. > > > > Look at this example > > > http://docs.codehaus.org/display/GMAVENPLUS/Examples#Examples-ExecuteScripts > > > > The user can write a trivial script launched like this > > > > > > > > and write a RunOrder servis by setting it in to execution property: > > > > <<someScript.groovy>> > > hook.set(new RunOrder()); > > > > Tha's it, very simple. > > All we need to do is to provide the execution property 'hook' - the name > is > > just for illustration purposes only. > > > > > > > > -- > > View this message in context: > http://maven.40175.n5.nabble.com/Plugable-Softcoded-Customized-Maven-Plugins-tp5823365p5823467.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 > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
