Hello Barrie, I know that :-) Our parent pom defines literally dozens of plugins, configures them *and* adds a few profiles which change the configuration and the plugins called on the existence of files, the environment (running in Jenkins?) and I hoped I could split stuff a bit.
Regards Mirko -- Sent from my mobile On Jul 6, 2013 8:17 AM, "Barrie Treloar" <baerr...@gmail.com> wrote: > On 6 July 2013 15:39, Mirko Friedenhagen <mfriedenha...@gmail.com> wrote: > > Hello there, > > > > is there a way to switch to a different lifecycle depending on e.g. a > > path/file etc? Or is the agreed way to just have another packaging? > > The lifecycle for the pom comes from packaging. > > The plugins that pom declares then attach themselves to the lifecycle > stages. > > You can always use a "pom" packaging to essentiallly do nothing, and > have all the work done via plugins. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
