javagoogle/guava #6612Not checked yet

Gradle Metadata of 32.1.0 has a SNAPSHOT version number

envgap__google__guava-6612

Original GitHub issue ↗Opened 2023-06-30

01 / FAILURE SIGNATURE

As reported upstream

No identifying execution failure has been captured.

Not checked yet.

No curated issue-specific recipe or verified environment fix is available.

02 / ENVIRONMENT RECIPE

Base commit: Not freshly verified
Manifest: pom.xml
Reproduce: Awaiting issue-specific recipe
Run under trace: Awaiting a meaningful runtime command

03 / ORIGINAL ISSUE TEXT

google/guava #6612 · read the original issue

I am very sorry @cpovirk but the Gradle Metadata just published is broken. If you look at these two files:

- https://repo1.maven.org/maven2/com/google/guava/guava/32.1.0-jre/guava-32.1.0-jre.module

- https://repo1.maven.org/maven2/com/google/guava/guava/32.1.0-android/guava-32.1.0-android.module



You see several versions like `HEAD-android-SNAPSHOT` in them. 



I believe this is because the `util/set_version.sh` script was not used to set the version [here](https://github.com/google/guava/commit/53bb66554b195ab3aec3da285f1f140b1abae44d).

My assumption was that this is somehow automatically used before each release. So I did not think about that further. I guess I was wrong and that's not the case. 😞 



These lines need to be executed on a version change:

https://github.com/google/guava/blob/master/util/set_version.sh#L18-L21



I am afraid this requires patching, as in certain situations the metadata now points at files not available on Maven Central.

Continue on GitHub ↗

04 / LABELS

Labels from the report text only; not yet run

No supported category has been assigned.

Label rules and the text that matched

[]

Issue-specific recipe and runtime smoke command require review against the complete issue and repository.

Legacy reproduction is generic install-only; match the actual issue failure before admission.