[
https://issues.apache.org/jira/browse/MNG-7885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17767940#comment-17767940
]
Tamas Cservenak commented on MNG-7885:
--------------------------------------
While this sounds good, I think this is a bad idea... build tools (plugins)
should be orthogonal to your project. Think all the "common" dependencies
(logging, commons, etc), many times your plugin and your project have wildly
different requirements.
IIUC you want to define a depMgt and that have applied to plugin dependencies?
As in that moment, for example your project and plugin would be obliged to use
same slf4j-api for example (just as an example of common dependency).
IMHO, current separation is cleaner: you define in depMgt project (what your
project uses) dependencies, and yes, while a bit laborious, you need to define
extra bits in plugin/dependencies as well.
Maybe just use properties for this?
* slf4j.version for project dependency versions
* plugin.slf4j.version for plugin dependency versions (and use expression in
plugin/dependency)
Other problem I see IF this get applied, is how to "opt out"? I bet there will
be users who does need and want what I wrote above (completely different
versions for project itself and plugins).
> 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)
