ChangeParentPom/RemoveRedundantDependencyVersion - removing dependency that has configuration (exclusion, scope, etc) #4386
-
We are noticing that these 2 recipes, which we really do need, are removing dependency configuration (exclusions) that we still need. I almost filed this as a bug; however, it's not crystal clear.. With the new version, it's not clear the exclusions would still be valid. Even so, I'm leaning towards that's the better option. I'm curious what others' think on this. Is it better to:
I have this failing
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Thanks for the runnable example! Logging the result of running the above test here, just to save folks a step. diff --git a/pom.xml b/pom.xml
index 9a1716e..348dd09 100644
--- a/pom.xml
+++ b/pom.xml
@@ -8,20 +8,6 @@
<groupId>com.example</groupId>
<artifactId>acme</artifactId>
<version>0.0.1-SNAPSHOT</version>
- <dependencyManagement>
- <dependencies>
- <dependency>
- <groupId>org.springframework.boot</groupId>
- <artifactId>spring-boot-starter-web</artifactId>
- <exclusions>
- <exclusion>
- <groupId>org.slf4j</groupId>
- <artifactId>slf4j-api</artifactId>
- </exclusion>
- </exclusions>
- </dependency>
- </dependencies>
- </dependencyManagement>
<dependencies>
<dependency>
<groupId>org.springframework.boot</groupId> |
Beta Was this translation helpful? Give feedback.
Let's discuss this over on an attached PR, as that makes the code run.