Open juergen3000 opened 1 year ago
It's really an awful amount of clutter that's added by this inadvertently - would be nice to have this removed again without having to declare exclusions in all projects depending on fst :)
Edit: Snippet with corresponding exclusion, if someone else needs it in the meantime:
<dependency>
<groupId>de.ruedigermoeller</groupId>
<artifactId>fst</artifactId>
<version>3.0.4-jdk17</version>
<exclusions>
<exclusion>
<groupId>org.apache.felix</groupId>
<artifactId>maven-bundle-plugin</artifactId>
</exclusion>
</exclusions>
</dependency>
Declaring the Dependency to the Maven Module
maven-bundle-plugin
in theDependencies
-Section like thisleads to the following Dependency Tree in
compile
-Scope, which means, you explicitly have to declare anexclusion
if you don't want to ship Maven Modules with Dependencies likejunit-4
with your Production Artifact.compile-Scope Dependency Tree:
Affected Versions:
3.0.3-jdk17
3.0.4-jdk17