Skip to content

Conversation

caiwei-ebay
Copy link
Contributor

@caiwei-ebay caiwei-ebay commented Aug 4, 2023

The app pom introduces A:1.0-RELEASE, and this artifact A has transitive dependency B:0.12.0-SNAPSHOT. In app pom, we manage B as version 0.13.0-RELEASE.

When the pmd:3.15.0 and above is being executed, it will resolve dependencies, and somehow the B:0.12.0-SNAPSHOT is resolved as a dependency instead of B:0.13.0-RELEASE.

This is not only downloading wrong version, but also means lots of transitive dependencies with unmanaged version will be always downloaded (if not in cache) causing build slowness. Especially when we are using BF option: -Daether.dependencyCollector.impl=bf, this algorithm will skip downloading poms of for conflict losers, but maven-pmd-plugin (having this bug) again downloads those skipped ones.

More details about BF:
https://issues.apache.org/jira/browse/MRESOLVER-324

@michael-o michael-o closed this in 96e5079 Aug 4, 2023
@jira-importer
Copy link

Resolve #352

1 similar comment
@jira-importer
Copy link

Resolve #352

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants