[MNG-7885] Plugin dependencies should be part in dependency management

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: Dependencies
• Assignee: Unassigned
• Reporter: Lars Uffmann
• Created: 15/Sep/23 07:25
• Updated: 22/Sep/23 12:13

Description

It would be a great improvement in dependency management if plugin dependencies could be part of the standard dependency management resolution. In the example below I could manage the version of the rewrite-maven-plugin using pluginManagement, the version of the rewrite-spring plugin dependency however has to be set in place.

 

 

<build>
  <plugins>
    <plugin>
      <groupId>org.openrewrite.maven</groupId>
      <artifactId>rewrite-maven-plugin</artifactId>
      <configuration>
        <activeRecipes>
          <recipe>org.openrewrite.java.spring.boot2.SpringBoot2JUnit4to5Migration</recipe>
        </activeRecipes>
      </configuration>
      <dependencies>
        <dependency>
          <groupId>org.openrewrite.recipe</groupId>
          <artifactId>rewrite-spring</artifactId>
          <version>4.35.0</version>
        </dependency>
      </dependencies>
    </plugin>
  </plugins>
<build>

 

 

Other plugins are using special configurations to declare extra dependencies. The version. management issue however is the same. A good example is   
annotationProcessorPaths of the compiler plugin.

Issue Links

• is related to: MCOMPILER-391 annotationProcessorPaths have to follow dependencyManagement rules