I'm talking about in the projects that use your plugin On 19 February 2010 09:19, tbee <t...@tbee.org> wrote:
> > > > Stephen Connolly-2 wrote: > > > > If you want to bind your plugin to pre-existing phases, then you must > > either > > create your own packaging type (will will require you to add your plugin > > with <extensions>true</extensions> IIRC) or you need to use <executions> > > to > > bind the plugin to the lifecycle of the packaging type you currently > have. > > > > Hm. It's my first plugin, so I'm not as secure on this as I would like to > be... > > The project was create as an archtype, so the packaging type is the > default. > > <packaging>maven-plugin</packaging> > > The plugin should execute as part of the package phase. I can just define > other packaging types? That is confusing. I would expect that I can define > an execution, and thus a phase where it should execute in, in the plugin's > pom. Together with the parameters and stuff. > -- > View this message in context: > http://old.nabble.com/custom-maven-plugin-default-phase-tp27626122p27651482.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 > >
