- 04 Oct, 2022 1 commit
-
-
林军华 authored
-
- 28 Jul, 2022 1 commit
-
-
Michael Goderbauer authored
-
- 12 Jul, 2022 1 commit
-
-
Alexandre Ardhuin authored
-
- 19 Apr, 2022 1 commit
-
-
Elsabe Ros authored
-
- 13 Apr, 2022 2 commits
-
-
Zachary Anderson authored
This reverts commit 2b0255f0.
-
Elsabe Ros authored
-
- 07 Apr, 2022 1 commit
-
-
Emmanuel Garcia authored
-
- 31 Mar, 2022 1 commit
-
-
Emmanuel Garcia authored
-
- 13 Jul, 2021 1 commit
-
-
Darren Austin authored
-
- 12 Jul, 2021 2 commits
-
-
Darren Austin authored
This reverts commit 9d3563a8.
-
Darren Austin authored
-
- 05 Jun, 2021 1 commit
-
-
Jenn Magder authored
-
- 19 May, 2021 1 commit
-
-
Hattomo (TomohiroHattori) authored
-
- 20 Apr, 2021 1 commit
-
-
Emmanuel Garcia authored
-
- 07 Oct, 2020 1 commit
-
-
Casey Hillers authored
-
- 22 Sep, 2020 1 commit
-
-
godofredoc authored
-
- 16 Sep, 2020 1 commit
-
-
Michael R Fairhurst authored
-
- 24 Jun, 2020 1 commit
-
-
Chris Yang authored
-
- 27 May, 2020 1 commit
-
-
Emmanuel Garcia authored
-
- 16 Jan, 2020 1 commit
-
-
sjindel-google authored
-
- 27 Nov, 2019 1 commit
-
-
Ian Hickson authored
* Update project.pbxproj files to say Flutter rather than Chromium Also, the templates now have an empty organization so that we don't cause people to give their apps a Flutter copyright. * Update the copyright notice checker to require a standard notice on all files * Update copyrights on Dart files. (This was a mechanical commit.) * Fix weird license headers on Dart files that deviate from our conventions; relicense Shrine. Some were already marked "The Flutter Authors", not clear why. Their dates have been normalized. Some were missing the blank line after the license. Some were randomly different in trivial ways for no apparent reason (e.g. missing the trailing period). * Clean up the copyrights in non-Dart files. (Manual edits.) Also, make sure templates don't have copyrights. * Fix some more ORGANIZATIONNAMEs
-
- 09 Nov, 2019 1 commit
-
-
Ian Hickson authored
-
- 07 Nov, 2019 1 commit
-
-
xster authored
-
- 02 Nov, 2019 1 commit
-
-
Emmanuel Garcia authored
-
- 21 Oct, 2019 1 commit
-
-
Emmanuel Garcia authored
-
- 09 Oct, 2019 1 commit
-
-
Emmanuel Garcia authored
-
- 30 Jul, 2019 1 commit
-
-
Emmanuel Garcia 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 } }
-