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.

Sign up for GitHub

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

Jump to bottom

Put the versions of dependencies directly in Gradle Metadata. #6667

Closed
wants to merge 1 commit into from
Closed

Put the versions of dependencies directly in Gradle Metadata. #6667

wants to merge 1 commit into from

Commits on Aug 2, 2023

  1. Put the versions of dependencies directly in Gradle Metadata. 

    This makes the version handling in POM and Gradle Metadata more similar.
See #6654 (comment)

We expect this to fix #6657, though we don't fully understand it.

Fixes #6664

RELNOTES=Changed Gradle Metadata to include dependency versions directly. This may address ["Could not find `some-dependency`" errors](#6657) that some users have reported (which might be a result of users' excluding `guava-parent`).
PiperOrigin-RevId: 553180806
    @jjohannes
    jjohannes authored and Google Java Core Libraries committed Aug 2, 2023
    Configuration menu
    Copy the full SHA
    4787cf5 View commit details
    Browse the repository at this point in the history