[
https://issues.apache.org/jira/browse/MNG-7885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17765490#comment-17765490
]
Slawomir Jaranowski commented on MNG-7885:
------------------------------------------
[~cachescrubber] for annotationProcessorPaths we have a fix: MCOMPILER-391
> Plugin dependencies should be part in dependency management
> -----------------------------------------------------------
>
> Key: MNG-7885
> URL: https://issues.apache.org/jira/browse/MNG-7885
> Project: Maven
> Issue Type: Improvement
> Components: Dependencies
> Reporter: Lars Uffmann
> Priority: Major
>
> 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.
>
>
> {code:java}
> <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>{code}
>
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
