[MNG-5588] Scope import in pluginManagement

[jira-importer]

Romain N opened MNG-5588 and commented

I can do this in dependencyManagement to define dependencies versions:

<dependencyManagement>
  <dependency>
    <groupId>test</groupId>
    <artifactId>test</artifactId>
    <version>1</version>
    <scope>import</scope>
    <type>pom</type>
  </dependency>
</dependencyManagement>

It could be great to can do the same things in pluginManagement to define version plugin and default behavior.

---

Affects: 3.1.1

Issue Links:

• MNG-6562 WARN if plugins injected by default lifecycle bindings don't have their version locked in pom.xml or parent

• MNG-5102 Mixin POM fragments

• MNG-3220 Allow managed dependencies to be imported into other projects

• MNG-7844 Support for DTD entities and XInclude in the code at build time

Remote Links:

• Page
  

84 votes, 103 watchers

[jira-importer]

F Carlsen commented

This would be great improvement and would helps share plugin configuration and standards across projects.

At the moment, the only way of sharing plugin configuration is through inheritance. Unfortunately, this isn't always feasible, and relying on inheritance for sharing configuration that only some children are going to need is a bad practice (e.g. violates Liskov's substition principle). Composition would be better than Inheritance for configuration anyway.

In a multi-module project, you will get a warning if you're trying to use parent pom's from different inheritance hierarchies, which says it may be disallowed in a future release, so there's really no decent alternatives today and I hope this feature gets prioritized.

[jira-importer]

Christian Roeder commented

Such a functionality would really be practial if you're stuck with Maven and can not do composition as it is possible with gradle.

[jira-importer]

Christian Schulte commented

There is no XML element scope available to pluginManagement/plugins.

The only available elements are groupId, artifactId and version.
None of these can be -abused- to support some kind of import.

[jira-importer]

Stephen Connolly commented

I think mix-ins is a more appropriate way to address this functional requirement

[jira-importer]

Peter Palaga commented

Stephen Connolly are mixins planned or being worked on? Can I find out more about them somewhere?

[jira-importer]

Deepak Abraham commented

Any chance this sees the light of day? This feature would be really useful...

[jira-importer]

Jeff Thomas commented

I would also love to see this feature.

I just implemented a 'dependencyManagement' import POM for all of the Axis2 dependencies that we need to keep synchronized over multiple projects without parent-inheritence.

However, Axis2 also provides several Maven Plugins which I would like to centrally manage the versions and base-configurations for as well.

The Mixin plugin still requires you to define plugin versions in the parent-poms...ideally I would want to do that centrally as with the dependencyManagement import POM.

[jira-importer]

Robert Scholte commented

Requires at least pom model 5.0.0, because plugins don't have a scope

[jira-importer]

Dmitry Ovchinnikov commented

The dependency version importing is a killer feature of Maven, it's a "declarative way" the Maven belongs to. It would be very useful to have something like that for plugins. Could it be like that?

<dependencyManagement>
  <dependency>
     <groupId>some-group-id</groupId>
     <artifactId>some-artifact-id</artifactId>
     <version>a-version</version>
     <scope>import-plugins</scope>
     <type>pom</type>
  </dependency>
</dependencyManagement>

So, we could have different scopes without changing the POM model: "import-dependencies" (an alias to "import"), "import-plugins", "import-properties" and so on.

[jira-importer]

jinyanan commented

It's a good feature which I need too.

[jira-importer]

Matthew Ouyang commented

Dmitry Ovchinnikov I would argue that both a new scope and MNG-5102 are unnecessary for this ticket.  If you're importing a pom then you import the whole thing, not just the dependencyManagement portion.  Maybe whatever part of the code that parses the pom and sets up dependencyManagement can be augmented to set up in pluginManagement as well.

[jira-importer]

Miroslav Zaťko commented

I think it is must have feature

[jira-importer]

Thomas Repnik commented

Can't believe such an import task is open since more than 5 years. If just one complex plugin configuration should be shared, maven enforces pom inheritance. This is a big design flaw.

[jira-importer]

Christophe Domas commented

It would be very useful for spring-boot project. A lot of stuff is done in the parent pom of spring boot. If you want to import your own parent pom, you can use the spring boot bom for dependencies but you'll have to redefine the plugin management section.

[jira-importer]

Yannick Valot commented

I think there might be a problem because a BOM is at the same time :

• The deliverable artefact
• The description of how to build and deliver the artefact itself

I have several projects where I need to specify an explicit version for maven-deploy-plugin, which I usually do through pluginManagement.

These projects provide, among other artefacts, a BOM to be imported by other projects.

It seems my BOMs (which have no parent) needs the pluginManagement in order to deploy themselves, but I do not wish projects importing my bom to be affected by this.

Maybe this particular case has another solution (maybe I would only need to specify the plugin directive and not the pluginManagement). Still we need to be careful to clearly limit what is imported from a BOM .