mirror of
https://github.com/flutter/flutter.git
synced 2025-06-03 00:51:18 +00:00
594ff98a65
Adds warning to `flutter create` command that checks if detected Java version is compatible with the template AGP and template Gradle versions. If a developer is building for Android and their Java version is incompatible with either the AGP or Gradle versions that Flutter currently supports by default for new Flutter projects, then - a warning will show noting the incompatibility and - steps will be shown to fix the issue, the recommended option being to configure a new compatible Java version given that Flutter knows we can support the template Gradle/AGP versions and updating them manually may be risky (feedback on this approach would be greatly appreciated!) Given that the template AGP and Gradle versions are compatible, this PR assumes that the detected Java version may only conflict with one of the template AGP or Gradle versions because: - the minimum Java version for a given AGP version is less than the maximum Java version compatible for the minimum Gradle version required for that AGP version (too low a Java version will fail AGP compatibility test, but not Gradle compatibility). - the maximum Java version compatible with minimum Gradle version for a given AGP version is higher than minimum Java version required for that AGP version (too high a Java version will fail Gradle compatibility test, but not AGP compatibility test). Fixes https://github.com/flutter/flutter/issues/130515 in the sense that `flutter create foo`; `cd foo`; `flutter run` should always be successful. |
||
|---|---|---|
| .. | ||
| app | ||
| app_integration_test/integration_test | ||
| app_shared | ||
| app_test_widget/test | ||
| cocoapods | ||
| module | ||
| package | ||
| package_ffi | ||
| plugin | ||
| plugin_ffi | ||
| plugin_shared | ||
| skeleton | ||
| xcode/ios/custom_application_bundle | ||
| README.md | ||
| template_manifest.json | ||
This directory contains templates for flutter create.
The *_shared subdirectories provide files for multiple templates.
app_sharedforappandskeleton.plugin_sharedfor (method channel)pluginandplugin_ffi.
For example, there are two app templates: app (the counter app)
and skeleton (the more advanced list view/detail view app).
┌────────────┐
│ app_shared │
└──┬──────┬──┘
│ │
│ │
▼ ▼
┌─────┐ ┌──────────┐
│ app │ │ skeleton │
└─────┘ └──────────┘
Thanks to app_shared, the templates for app and skeleton can contain
only the files that are specific to them alone, and the rest is automatically
kept in sync.