Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dependency convergence error: org.apiguardian:apiguardian-api #1920

Open
commonquail opened this issue Sep 24, 2024 · 0 comments
Open

Dependency convergence error: org.apiguardian:apiguardian-api #1920

commonquail opened this issue Sep 24, 2024 · 0 comments
Labels

Comments

@commonquail
Copy link

Logbook 3.9.0 suffers a dependency convergence error with org.apiguardian:apiguardian-api 1.1.1 and 1.1.2, causing difficulties with usage in Maven projects that enable that Enforcer rule.

Description

Since #1082, every Logbook artifact pulls in org.apiguardian:apiguardian-api:1.1.2. They also pull in org.zalando:faux-pas:0.9.0, which uses org.apiguardian:apiguardian-api:1.1.1, all of them in compile scope. Any Maven project that enables the Enforcer plugin's <dependencyConvergence/> rule will be prevented from building until org.apiguardian:apiguardian-api is transitively excluded and defined locally.

Possible Fix

  • Bump org.apiguardian:apiguardian-api in faux-pas, then bump faux-pas.
  • Revert Bump apiguardian-api from 1.1.1 to 1.1.2 #1082.
  • Exclude org.apiguardian:apiguardian-api from the faux-pas dependency declaration.
  • Mark org.apiguardian:apiguardian-api optional.
    • This is not addressed by the upstream project, but this really looks like the type of dependency that has no business being pulled into transitive compile scope by default. It contributes nothing to a downstream consumer at compile time.
    • I have not verified that this particular suggestion suffices.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant