Re: [jira] [Created] (MPOM-215) Create a new parent POM to lock down plugins versions of default lifecycle bindings

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: [jira] [Created] (MPOM-215) Create a new parent POM to lock down plugins versions of default lifecycle bindings

rfscholte
Introducing a new parent might help for some, but not for everybody.
If you already have a parent specified, you can't use this.
And Maven doesn't support mixins (yet).

We need to document how plugins are controlled.
These are probably all variants I can think of
- pom.xml
- via packaging-plugin
- parent (custom or new maven-defaults-plugins)
- super pom
- maven core

thanks,
Robert

On Mon, 14 Jan 2019 12:01:00 +0100, Hervé Boutemy (JIRA) <[hidden email]>  
wrote:

> Hervé Boutemy created MPOM-215:
> ----------------------------------
>
>              Summary: Create a new parent POM to lock down plugins  
> versions of default lifecycle bindings
>                  Key: MPOM-215
>                  URL: https://issues.apache.org/jira/browse/MPOM-215
>              Project: Maven POMs
>           Issue Type: New Feature
>             Reporter: Hervé Boutemy
>
>
> while working on version upgrade of default plugin bindings, we found  
> that:
> 1. a warning should be displayed MNG-6562
> 2. a parent POM would be the easiest solution to lock down every plugins  
> at once, instead of letting users lock down each plugin separately
>
> let's create this parent POM
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [jira] [Created] (MPOM-215) Create a new parent POM to lock down plugins versions of default lifecycle bindings

stephenconnolly
<inherit>false</inherit> in the executions?

On Tue, 15 Jan 2019 at 16:04, Hervé BOUTEMY <[hidden email]> wrote:

> initial content published, as a branch in maven-studies [1]
>
> I have a few issues that currently will block any release:
> 1. how to configure release plugin without leaking into future projects
> that
> will inherit?
> 2. how to configure invoker also to be able to create ITs to check that it
> works as expected?
>
> On documenting, I started the index.apt.
> Currently, packaging plugins do nothing in general, since it's Maven core
> that
> does the job: I'm curious to see how archetype-packaging is injected when
> configured as extension [2]. But I'm sure that we could override Maven
> core's
> default bindings: the only requirement will be to make the effort to
> create
> dedicated packaging artifacts, to avoid putting the whole plugin's
> dependencies in core classloader
>
> feedback welcome
>
> Regards,
>
> Hervé
>
> [1] https://github.com/apache/maven-studies/tree/maven-default-plugins
>
> [2] https://maven.apache.org/archetype/archetype-packaging/
>
> Le lundi 14 janvier 2019, 23:21:05 CET Robert Scholte a écrit :
> > Introducing a new parent might help for some, but not for everybody.
> > If you already have a parent specified, you can't use this.
> > And Maven doesn't support mixins (yet).
> >
> > We need to document how plugins are controlled.
> > These are probably all variants I can think of
> > - pom.xml
> > - via packaging-plugin
> > - parent (custom or new maven-defaults-plugins)
> > - super pom
> > - maven core
> >
> > thanks,
> > Robert
> >
> > On Mon, 14 Jan 2019 12:01:00 +0100, Hervé Boutemy (JIRA) <
> [hidden email]>
> >
> > wrote:
> > > Hervé Boutemy created MPOM-215:
> > > ----------------------------------
> > >
> > >              Summary: Create a new parent POM to lock down plugins
> > >
> > > versions of default lifecycle bindings
> > >
> > >                  Key: MPOM-215
> > >                  URL: https://issues.apache.org/jira/browse/MPOM-215
> > >
> > >              Project: Maven POMs
> > >
> > >           Issue Type: New Feature
> > >
> > >             Reporter: Hervé Boutemy
> > >
> > > while working on version upgrade of default plugin bindings, we found
> > > that:
> > > 1. a warning should be displayed MNG-6562
> > > 2. a parent POM would be the easiest solution to lock down every
> plugins
> > > at once, instead of letting users lock down each plugin separately
> > >
> > > let's create this parent POM
> > >
> > >
> > >
> > > --
> > > This message was sent by Atlassian JIRA
> > > (v7.6.3#76005)
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [jira] [Created] (MPOM-215) Create a new parent POM to lock down plugins versions of default lifecycle bindings

Hervé BOUTEMY
In reply to this post by rfscholte
work done: you can see the SNAPSHOT result at
https://maven.apache.org/pom-archives/default-plugins-LATEST/

the source is currently in a maven-studies branch:
https://github.com/apache/maven-studies/tree/maven-default-plugins


The is the question of what version to choose and when to release this POM?
I had a new idea: why not make this POM part of Maven core release?
This would clearly show that Apache Maven is not only core but also the
plugins. And this would give a natural rhythm to releases, that people would
understand. Last but not least: this would remove the release configuration
that was not really leaking, but at least was visible

This idea is implemented in MPOM-215 branch of Maven core.
The only issue I found is how to publish the documentation site: I suppose
we'll find a solution.

WDYT?

Regards,

Hervé

Le mardi 15 janvier 2019, 17:04:27 CET Hervé BOUTEMY a écrit :

> initial content published, as a branch in maven-studies [1]
>
> I have a few issues that currently will block any release:
> 1. how to configure release plugin without leaking into future projects that
> will inherit?
> 2. how to configure invoker also to be able to create ITs to check that it
> works as expected?
>
> On documenting, I started the index.apt.
> Currently, packaging plugins do nothing in general, since it's Maven core
> that does the job: I'm curious to see how archetype-packaging is injected
> when configured as extension [2]. But I'm sure that we could override Maven
> core's default bindings: the only requirement will be to make the effort to
> create dedicated packaging artifacts, to avoid putting the whole plugin's
> dependencies in core classloader
>
> feedback welcome
>
> Regards,
>
> Hervé
>
> [1] https://github.com/apache/maven-studies/tree/maven-default-plugins
>
> [2] https://maven.apache.org/archetype/archetype-packaging/
>
> Le lundi 14 janvier 2019, 23:21:05 CET Robert Scholte a écrit :
> > Introducing a new parent might help for some, but not for everybody.
> > If you already have a parent specified, you can't use this.
> > And Maven doesn't support mixins (yet).
> >
> > We need to document how plugins are controlled.
> > These are probably all variants I can think of
> > - pom.xml
> > - via packaging-plugin
> > - parent (custom or new maven-defaults-plugins)
> > - super pom
> > - maven core
> >
> > thanks,
> > Robert
> >
> > On Mon, 14 Jan 2019 12:01:00 +0100, Hervé Boutemy (JIRA) <[hidden email]>
> >
> > wrote:
> > > Hervé Boutemy created MPOM-215:
> > > ----------------------------------
> > >
> > >              Summary: Create a new parent POM to lock down plugins
> > >
> > > versions of default lifecycle bindings
> > >
> > >                  Key: MPOM-215
> > >                  URL: https://issues.apache.org/jira/browse/MPOM-215
> > >              
> > >              Project: Maven POMs
> > >          
> > >           Issue Type: New Feature
> > >          
> > >             Reporter: Hervé Boutemy
> > >
> > > while working on version upgrade of default plugin bindings, we found
> > > that:
> > > 1. a warning should be displayed MNG-6562
> > > 2. a parent POM would be the easiest solution to lock down every plugins
> > > at once, instead of letting users lock down each plugin separately
> > >
> > > let's create this parent POM
> > >
> > >
> > >
> > > --
> > > This message was sent by Atlassian JIRA
> > > (v7.6.3#76005)
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]





---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]