Op Tue, 26 Jan 2016 14:29:15 +0100 schreef Paul Benedict
<[email protected]>:
I'm more curious of the growth of "skip" parameters of plugins. Do they
exist really to skip the plugin, or are they really representative of the
desire to skip an entire phase?
On Jan 25, 2016 7:24 PM, "Christopher" <[email protected]> wrote:
I'm curious that growth too. It could also mean that we do something wrong.
I've been talking with Karl-Heinz about this and his reason is interesting.
He has a huge multimodule project, which he wants to deploy in the end,
but actually he's first interested if the changes make the whole project
still compilable.
Also in this case the skip parameter is a hack. Instead the lifecycle
handling should be improved, so users can specify the phases which should
be executed first before continuing. This requirement seems to be an extra
feature for MNG-5885[1].
thanks,
Robert
[1] https://issues.apache.org/jira/browse/MNG-5885
On Mon, Jan 25, 2016 at 2:51 PM, Robert Scholte <[email protected]>
wrote:
> Hi,
>
> I really wonder why it is useful to add a skip-parameter to the
packaging
> plugin? The goal for every Maven project is to end up with some
(packaged)
> artifact, right?
> A skip-parameter because a lot of other plugins have it as well is
IMHO
not
> a good reason, so what would be a valid usecase here?
>
I would argue that it's useful to be able to skip over arbitrary
plugins, regardless of what they do, simply for testing other parts of
the build.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
