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) <[email protected]>
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: [email protected]
For additional commands, e-mail: [email protected]
