-
Notifications
You must be signed in to change notification settings - Fork 28.5k
[flutter_tools] Migrate platforms away from .flutter-plugins #48918
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
Comments
Is this a duplicate of #39657? |
Oh never mind this is the cleanup step. |
Is the migration on this complete? |
It's still being parsed:
|
Looks like we're still parsing this in 2023: https://github.com/flutter/flutter/blob/master/packages/flutter_tools/gradle/src/main/groovy/flutter.groovy#L543 |
There may are projects, which were created with an old Edit: it also states to remove |
Relands #97823 When the tool migrated to `.flutter-plugins-dependencies`, the Gradle plugin was never changed. Until now, the plugin had the heuristic that a plugin with a `android/build.gradle` file supported the Android platform. Also applies schema of `getPluginDependencies` to `getPluginList` which uses a `List` of Object instead of `Properties`. Fixes #97729 Cause of the error: https://github.com/flutter/flutter/blob/5f105a6ca7a5ac7b8bc9b241f4c2d86f4188cf5c/packages/flutter_tools/gradle/flutter.gradle#L421C25-L421C25 Fixes #98048 The deprecated line `include ":$name"` in `settings.gradle` (pluginEach) in old projects causes the `project.rootProject.findProject` to also find the plugin "project", so it is not failing on the `afterEvaluate` method. But the plugin shouldn't be included in the first place as it fails with `Could not find method implementation() for arguments` error in special cases. Related to #48918, see [_writeFlutterPluginsListLegacy](https://github.com/flutter/flutter/blob/27bc1cf61a5b54bf655062be63050123abb617e4/packages/flutter_tools/lib/src/flutter_plugins.dart#L248). Co-authored-by: Emmanuel Garcia <[email protected]>
This is now solved in #137115 I think #54566 is obsolete due to #135392 and we can remove all the |
Relands flutter#97823 When the tool migrated to `.flutter-plugins-dependencies`, the Gradle plugin was never changed. Until now, the plugin had the heuristic that a plugin with a `android/build.gradle` file supported the Android platform. Also applies schema of `getPluginDependencies` to `getPluginList` which uses a `List` of Object instead of `Properties`. Fixes flutter#97729 Cause of the error: https://github.com/flutter/flutter/blob/5f105a6ca7a5ac7b8bc9b241f4c2d86f4188cf5c/packages/flutter_tools/gradle/flutter.gradle#L421C25-L421C25 Fixes flutter#98048 The deprecated line `include ":$name"` in `settings.gradle` (pluginEach) in old projects causes the `project.rootProject.findProject` to also find the plugin "project", so it is not failing on the `afterEvaluate` method. But the plugin shouldn't be included in the first place as it fails with `Could not find method implementation() for arguments` error in special cases. Related to flutter#48918, see [_writeFlutterPluginsListLegacy](https://github.com/flutter/flutter/blob/27bc1cf61a5b54bf655062be63050123abb617e4/packages/flutter_tools/lib/src/flutter_plugins.dart#L248). Co-authored-by: Emmanuel Garcia <[email protected]>
@Gustl22 What's the deprecation period in this case? Will it start counting when the next Flutter stable is released and the imperative |
@bartekpacia I'm not that familiar with the process. But it then has the same cycle as the imperative |
Work towards flutter/flutter#48918. --------- Co-authored-by: Shams Zakhour (ignore Sfshaza) <[email protected]>
…` file. (#157388)" (#157541) Reverts: #157388 Initiated by: matanlurey Reason for reverting: We have `--fatal-warnings` on postsubmit and this breaks the tree. Original PR Author: matanlurey Reviewed By: {reidbaker} This change reverts the following previous change: Work towards #48918. This file was soft deprecated in _2020_, but the code was never removed. This warning message will serve as a warning and we'll rip out support for `flutter-plugins` after the _next_ stable release (i.e. after the mid-November branch cut).
…r-plugins` file. (#157388)" (#157541)" (#157549) Reverts: #157541 Initiated by: matanlurey Reason for reverting: Was _not_ the cause of failure, see #157542. Original PR Author: auto-submit[bot] Reviewed By: {fluttergithubbot} This change reverts the following previous change: Reverts: #157388 Initiated by: matanlurey Reason for reverting: We have `--fatal-warnings` on postsubmit and this breaks the tree. Original PR Author: matanlurey Reviewed By: {reidbaker} This change reverts the following previous change: Work towards #48918. This file was soft deprecated in _2020_, but the code was never removed. This warning message will serve as a warning and we'll rip out support for `flutter-plugins` after the _next_ stable release (i.e. after the mid-November branch cut).
…t`. (#157527) Work towards #48918. Workaround for #157391 (see #157393 (comment)). I'll run all post-submit tasks as well on this PR using `test: all`.
…lutter#157388) Work towards flutter#48918. This file was soft deprecated in _2020_, but the code was never removed. This warning message will serve as a warning and we'll rip out support for `flutter-plugins` after the _next_ stable release (i.e. after the mid-November branch cut).
As of the latest master, this is true behind the flag |
As of the latest master (#160289), this is true by default. After the next stable release, the ability to opt-out will be removed, and the feature can be removed. |
#48614 moves the plugins list to
.flutter-plugins-dependencies
..flutter-plugins
will be kept for a whilee to avoid breaking existing apps, but should be removed after the migration is completeThe text was updated successfully, but these errors were encountered: