-
Notifications
You must be signed in to change notification settings - Fork 3.5k
[various] Standardize Java compat in Gradle #10091
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
[various] Standardize Java compat in Gradle #10091
Conversation
Standardize `sourceCompatibility and targetCompatibility on the `=` form of property assignment. Part of flutter/flutter#176065
|
CHANGELOG/version override: this is a no-op style change, so doesn't impact clients. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request standardizes the property assignment for sourceCompatibility and targetCompatibility in Gradle files across the repository, using the = syntax for consistency. The change is applied to numerous build.gradle files, and is also reflected in related documentation and validation scripts.
Piinks
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
RSLGTM
chunhtai
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
autosubmit label was removed for flutter/packages/10091, because - The status or check suite Mac_arm64 ios_platform_tests_shard_3 master has failed. Please fix the issues identified (or deflake) before re-applying this label. |
|
autosubmit label was removed for flutter/packages/10091, because - The status or check suite Mac_arm64 ios_platform_tests_shard_3 master has failed. Please fix the issues identified (or deflake) before re-applying this label. |
flutter/packages@389c678...34eec78 2025-09-29 blackorbs.dev@gmail.com [camera_android_camerax] Implement setDescriptionWhileRecording (flutter/packages#10030) 2025-09-29 49699333+dependabot[bot]@users.noreply.github.com [dependabot]: Bump org.jetbrains.kotlin:kotlin-bom from 2.0.21 to 2.2.20 in /packages/pigeon/platform_tests/test_plugin/android (flutter/packages#10114) 2025-09-27 stuartmorgan@google.com [various] Standardize Java compat in Gradle (flutter/packages#10091) 2025-09-26 stuartmorgan@google.com [various] Standardize gradle dependencies (flutter/packages#10083) 2025-09-26 paulberry@google.com [go_router_builder] Ignore upcoming `experimental_member_use` warnings. (flutter/packages#10082) 2025-09-26 stuartmorgan@google.com [various] Standardize Gradle `namespace` (flutter/packages#10084) If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/flutter-packages-flutter-autoroll Please CC flutter-ecosystem@google.com on the revert to ensure that a human is aware of the problem. To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Standardize
sourceCompatibility and targetCompatibility on the=` form of property assignment.Part of flutter/flutter#176065
Pre-Review Checklist
[shared_preferences]pubspec.yamlwith an appropriate new version according to the pub versioning philosophy, or I have commented below to indicate which version change exemption this PR falls under1.CHANGELOG.mdto add a description of the change, following repository CHANGELOG style, or I have commented below to indicate which CHANGELOG exemption this PR falls under1.///).Footnotes
Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling. ↩ ↩2 ↩3