What do you think is unclear about the default lifecycle that you augment by adding new executions to a particular phase in the lifecycle? You can also make your own lifecycle if you wish but for the most part the default lifecycle is sufficient. Or even cahnge all the bindings for the default lifecycle. For the Takari Lifecycle which has completely different implementations we didn't need any changes to the default lifecycle we just bound new implementations.
There is also nothing stopping you from adding extensions points to plugins. You can do that today, the enforcer plugin being a case in point. This mechanism already exists where you can create an extension point as a collection that gets injected into a plugin, and new implementations of the extension will be loaded dynamically when added as dependencies to that plugin in the POM. We can add this to any plugin today. If you wanted to provide an extension point to the maven-jar-plugin to filter the manifest before writing it into the JAR you can do that now. On Jan 15, 2015, at 5:57 AM, Tibor Digana <tibordig...@apache.org> wrote: > Maybe Jason can bring some light into this discussion. > Jason? > > > > -- > View this message in context: > http://maven.40175.n5.nabble.com/Plugable-Softcoded-Customized-Maven-Plugins-tp5823365p5823611.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 > Thanks, Jason ---------------------------------------------------------- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io --------------------------------------------------------- happiness is like a butterfly: the more you chase it, the more it will elude you, but if you turn your attention to other things, it will come and sit softly on your shoulder ... -- Thoreau --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
