I think there are some little inconsistencies in vocabulary, causing wrong
analysis
there are 3 lifecycles: default, clean and site [1]
and packaging selects default plugin bindings for default lifecycle [2]
For the moment, I didn't dig sufficiently into everything to have every answers
and r
So what I am saying it that its only the packaging the defines which
lifecycle will be used.
You can't use files/paths.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven
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
-
On 6 July 2013 15:39, Mirko Friedenhagen 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
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?
Regards Mirko
--
Sent from my mobile
