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

java-analytics-admin/google-analytics-admin-bom/pom.xml contains artifacts with invalid group ID #9304

Closed
suztomo opened this issue Apr 3, 2023 · 0 comments · Fixed by googleapis/synthtool#1787
Assignees
Labels
priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@suztomo
Copy link
Member

suztomo commented Apr 3, 2023

java.io.IOException: Received 404 response from invalid artifact https://repo1.maven.org/maven2/com/google/analytics/api/grpc/grpc-google-analytics-admin-v1alpha/0.24.0/
	at com.google.cloud.BomContentTest.assertReachable(BomContentTest.java:180)
	at com.google.cloud.BomContentTest.checkBomReachable(BomContentTest.java:99)

The change to the java-analytics-admin/google-analytics-admin-bom/pom.xml happened in
https://github.com/googleapis/google-cloud-java/pull/9261/files#diff-1cede8d4c034746d4625dc0ac2f198d7d6fb1cbd339f51fc2d22b0f6e3dc8bc2R33 (5 days ago)
The template change happened in googleapis/synthtool#1770

@suztomo suztomo added type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. labels Apr 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants