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

Migrate the generated Gradle files to be compatible with Java 22 #3125

Open
blakeli0 opened this issue Aug 19, 2024 · 0 comments
Open

Migrate the generated Gradle files to be compatible with Java 22 #3125

blakeli0 opened this issue Aug 19, 2024 · 0 comments
Assignees
@blakeli0
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Comments

@blakeli0
Copy link
Collaborator

The generated Gradle files as part of the self service(Bazel) flow includes configurations that are not compatible with Java 22.

  1. The gradle-wrapper.properties references 7.6.4 which does not support Java 22. The earliest Gradle version that supports Java 22 is 8.8 per compatibility table.
  2. There are a few templates reference classifier, which has been deprecated since 5.1 and removed since 8.0.

We need to migrate these files to be compatible with Java 22, but also stay compatible with Java 8 and Gradle 7.x.
@blakeli0 blakeli0 added type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. priority: p2 Moderately-important priority. Fix may not be included in next release. labels Aug 19, 2024
@blakeli0 blakeli0 self-assigned this Aug 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@blakeli0 blakeli0

Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@blakeli0