- 07 Oct, 2019 1 commit
-
-
Zachary Anderson authored
-
- 06 Oct, 2019 1 commit
-
-
Ian Hickson authored
* Minor clean-up in terminal.dart * Don't wrap text in tests (otherwise we'll be sensitive to the terminal width).
-
- 04 Oct, 2019 2 commits
-
-
Emmanuel Garcia authored
* Generate projects using the new Android embedding * Add comment about usesNewEmbedding:true * Feedback * Rework way to detect new embedding in new apps
-
Alexandre Ardhuin authored
-
- 03 Oct, 2019 1 commit
-
-
Zachary Anderson authored
-
- 30 Sep, 2019 1 commit
-
-
Zachary Anderson authored
* [flutter_tool] Report to analytics when the tool is killed by a signal * Fix analyzer lint
-
- 24 Sep, 2019 2 commits
-
-
Emmanuel Garcia authored
-
Alexandre Ardhuin authored
-
- 23 Sep, 2019 1 commit
-
-
Emmanuel Garcia authored
This reverts commit 96482eeb.
-
- 20 Sep, 2019 1 commit
-
-
Emmanuel Garcia authored
-
- 29 Jul, 2019 1 commit
-
-
Zachary Anderson authored
-
- 24 Jul, 2019 1 commit
-
-
Ian Hickson authored
-
- 23 Jul, 2019 3 commits
-
-
Emmanuel Garcia authored
`flutter build aar` This new build command works just like `flutter build apk` or `flutter build appbundle`, but for plugin and module projects. This PR also refactors how plugins are included in app or module projects. By building the plugins as AARs, the Android Gradle plugin is able to use Jetifier to translate support libraries into AndroidX libraries for all the plugin's native code. Thus, reducing the error rate when using AndroidX in apps. This change also allows to build modules as AARs, so developers can take these artifacts and distribute them along with the native host app without the need of the Flutter tool. This is a requirement for add to app. `flutter build aar` generates POM artifacts (XML files) which contain metadata about the native dependencies used by the plugin. This allows Gradle to resolve dependencies at the app level. The result of this new build command is a single build/outputs/repo, the local repository that contains all the generated AARs and POM files. In a Flutter app project, this local repo is used by the Flutter Gradle plugin to resolve the plugin dependencies. In add to app case, the developer needs to configure the local repo and the dependency manually in `build.gradle`: repositories { maven { url "<path-to-flutter-module>build/host/outputs/repo" } } dependencies { implementation("<package-name>:flutter_<build-mode>:1.0@aar") { transitive = true } }
-
Emmanuel Garcia authored
This reverts commit 11460b83.
-
Emmanuel Garcia authored
`flutter build aar` This new build command works just like `flutter build apk` or `flutter build appbundle`, but for plugin and module projects. This PR also refactors how plugins are included in app or module projects. By building the plugins as AARs, the Android Gradle plugin is able to use Jetifier to translate support libraries into AndroidX libraries for all the plugin's native code. Thus, reducing the error rate when using AndroidX in apps. This change also allows to build modules as AARs, so developers can take these artifacts and distribute them along with the native host app without the need of the Flutter tool. This is a requirement for add to app. `flutter build aar` generates POM artifacts (XML files) which contain metadata about the native dependencies used by the plugin. This allows Gradle to resolve dependencies at the app level. The result of this new build command is a single build/outputs/repo, the local repository that contains all the generated AARs and POM files. In a Flutter app project, this local repo is used by the Flutter Gradle plugin to resolve the plugin dependencies. In add to app case, the developer needs to configure the local repo and the dependency manually in `build.gradle`: repositories { maven { url "<path-to-flutter-module>build/host/outputs/repo" } } dependencies { implementation("<package-name>:flutter_<build-mode>:1.0@aar") { transitive = true } }
-
- 22 Jul, 2019 3 commits
-
-
Jonah Williams authored
-
Jonah Williams authored
This reverts commit bd52a78c.
-
Jonah Williams authored
-
- 18 Jul, 2019 1 commit
-
-
Todd Volkert authored
This is a partial re-application of #24669, which was reverted due to Fuchsia breakages. https://github.com/flutter/flutter/issues/24413
-
- 17 Jul, 2019 1 commit
-
-
Todd Volkert authored
Update `FakeHttpClientResponse` to be impervious to Dart SDK changes to the `HttpClientResponse` stream type (between `List<int>` and `Uint8List`).
-
- 16 Jul, 2019 1 commit
-
-
Todd Volkert authored
Slight cleanup of file locations in flutter_tools to make it easier to see which files are responsible for data reporting.
-
- 11 Jul, 2019 1 commit
-
-
Jonah Williams authored
-
- 08 Jul, 2019 1 commit
-
-
Jonah Williams authored
-
- 03 Jul, 2019 1 commit
-
-
Jonah Williams authored
-
- 02 Jul, 2019 1 commit
-
-
Alexandre Ardhuin authored
* more ui-as-code * address review comments
-
- 27 Jun, 2019 1 commit
-
-
Jonah Williams authored
* fix multiroot builds * remove shout * add basic test * Update web_compilation_delegate.dart * Address review feedback * Update multiroot_asset_reader_test.dart * Update multiroot_asset_reader_test.dart * remove unpassable test * fix for windows * facepalm
-
- 10 Jun, 2019 3 commits
-
-
Jonah Williams authored
-
Jonah Williams authored
-
Jonah Williams authored
-
- 30 May, 2019 1 commit
-
-
Jonah Williams authored
-
- 20 May, 2019 1 commit
-
-
Sam Rawlins authored
-
- 30 Apr, 2019 1 commit
-
-
Jonah Williams authored
-