1. 23 Sep, 2019 1 commit
  2. 20 Sep, 2019 2 commits
  3. 18 Sep, 2019 1 commit
    • Amir Hardon's avatar
      Exclude non Android plugins from Gradle build (#40640) · 4e108b6f
      Amir Hardon authored
      Before this change, having an Android app depend on a plugin that has no android implementation resulted in a Gradle build failure.
      
      This scenario is likely to become more common if we're enabling federated plugins, as the package implementing just the desktop implementation of a plugin won't have an Android implementation.
      
      This changes the Gradle plugin to not try to build any plugins that doesn't have an android/build.gradle file.
      4e108b6f
  4. 17 Sep, 2019 1 commit
  5. 16 Sep, 2019 1 commit
  6. 14 Sep, 2019 2 commits
  7. 13 Sep, 2019 1 commit
  8. 11 Sep, 2019 1 commit
  9. 04 Sep, 2019 1 commit
  10. 03 Sep, 2019 1 commit
  11. 02 Sep, 2019 1 commit
  12. 29 Jul, 2019 1 commit
  13. 23 Jul, 2019 3 commits
    • Emmanuel Garcia's avatar
      Flutter build aar (#36732) · 242a4225
      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
          }
      }
      242a4225
    • Emmanuel Garcia's avatar
      Revert "Add flutter build aar (#35217)" (#36731) · c9b466f9
      Emmanuel Garcia authored
      This reverts commit 11460b83.
      c9b466f9
    • Emmanuel Garcia's avatar
      Add flutter build aar (#35217) · 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
          }
      }
      11460b83
  14. 17 Jul, 2019 1 commit
  15. 25 Jun, 2019 1 commit
  16. 23 Jun, 2019 1 commit
  17. 19 Jun, 2019 1 commit
  18. 18 Jun, 2019 2 commits
  19. 17 Jun, 2019 2 commits
  20. 13 Jun, 2019 1 commit
  21. 11 Jun, 2019 1 commit
  22. 10 Jun, 2019 1 commit
  23. 09 Jun, 2019 2 commits
  24. 28 May, 2019 1 commit
  25. 22 May, 2019 1 commit
  26. 20 May, 2019 1 commit
  27. 01 May, 2019 1 commit
  28. 06 Mar, 2019 1 commit
  29. 30 Jan, 2019 1 commit
  30. 24 Jan, 2019 2 commits
  31. 18 Jan, 2019 1 commit
  32. 16 Jan, 2019 1 commit