Use-case for multiple <plugin> entries in the same <plugins> section

View: New views
3 Messages — Rating Filter:   Alert me  

Use-case for multiple <plugin> entries in the same <plugins> section

by Stephen Connolly-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Just thought of a use-case for listing the same plugin twice in the
one <plugins> section.... namely <inherited>true</inherited> and
<inherited>false</inherited>

OK, so it's somewhat specialised, and I have not had to use it myself,
and you could probably work-around using a profile, but there is a use
case.

So what I would say is than in any one <plugins> section, the
groupId:artifactId:inherited should be unique for each <plugin> in the
<plugins> section

-Stephen

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...


Re: Use-case for multiple <plugin> entries in the same <plugins> section

by BRIAN FOX-5 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

You should use the inherited element of the execution for that.

On Wed, Nov 11, 2009 at 4:43 AM, Stephen Connolly
<stephen.alan.connolly@...> wrote:

> Just thought of a use-case for listing the same plugin twice in the
> one <plugins> section.... namely <inherited>true</inherited> and
> <inherited>false</inherited>
>
> OK, so it's somewhat specialised, and I have not had to use it myself,
> and you could probably work-around using a profile, but there is a use
> case.
>
> So what I would say is than in any one <plugins> section, the
> groupId:artifactId:inherited should be unique for each <plugin> in the
> <plugins> section
>
> -Stephen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...


Re: Use-case for multiple <plugin> entries in the same <plugins> section

by Stephen Connolly-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

but what if you want to configure the defaults for all executions, and for
the child module executions, and you want the defaults for the child modules
to be different from the defaults for this module.

e.g.

turn skip on for this module, but off for child modules

2009/11/12 Brian Fox <brianf@...>

> You should use the inherited element of the execution for that.
>
> On Wed, Nov 11, 2009 at 4:43 AM, Stephen Connolly
> <stephen.alan.connolly@...> wrote:
> > Just thought of a use-case for listing the same plugin twice in the
> > one <plugins> section.... namely <inherited>true</inherited> and
> > <inherited>false</inherited>
> >
> > OK, so it's somewhat specialised, and I have not had to use it myself,
> > and you could probably work-around using a profile, but there is a use
> > case.
> >
> > So what I would say is than in any one <plugins> section, the
> > groupId:artifactId:inherited should be unique for each <plugin> in the
> > <plugins> section
> >
> > -Stephen
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@...
> > For additional commands, e-mail: dev-help@...
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>
>