1. 20 Nov, 2021 1 commit
  2. 07 Nov, 2021 1 commit
  3. 05 Nov, 2021 3 commits
  4. 16 Aug, 2021 1 commit
  5. 20 Apr, 2021 1 commit
  6. 05 Mar, 2021 1 commit
  7. 02 Dec, 2020 1 commit
  8. 23 Nov, 2020 1 commit
  9. 20 Nov, 2020 1 commit
  10. 11 Aug, 2020 1 commit
  11. 04 Aug, 2020 2 commits
  12. 13 Feb, 2020 1 commit
  13. 04 Oct, 2019 1 commit
  14. 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
  15. 01 Jun, 2019 1 commit
  16. 19 Jan, 2019 1 commit
  17. 15 Jan, 2019 1 commit
  18. 10 Oct, 2018 1 commit
    • Greg Spencer's avatar
      Rename 'application' back to 'module', and make 'app' the default again for templates. (#22888) · 0ff9e8a9
      Greg Spencer authored
      We decided that redefining the default for templates was premature. We're going to go back to having "module" in experimental land again, and we'll try again when we have the feature set fully baked.
      
      This keeps the writing of the .metadata files, and writing the template type to them, because that was a good improvement, and there are still a bunch of added tests that improve our coverage.
      0ff9e8a9
  19. 04 Oct, 2018 1 commit
    • Greg Spencer's avatar
      Rename module --> application in flutter create command. (#22565) · 9f23866a
      Greg Spencer authored
      This renames the "module" template to the "application" template, and makes "application" the default. The existing "app" template is now deprecated.
      
      flutter create also now recognizes the type of project in an existing directory, and is able to recreate it without having the template type explicitly specified (although you can still do that). It does this now by first looking in the .metadata file for the new project_type field, and if it doesn't find that, then it looks at the directory structure. Also, the .metadata file is now overwritten even on an existing directory so that 1) the project_type can be added to legacy projects, and 2) the version of Flutter that updated the project last is updated.
      
      I also cleaned up a bunch of things in create_test.dart, added many more tests, and added an example test to the test/ directory in the generated output of the application template.
      
      Fixes #22530
      Fixes #22344
      9f23866a
  20. 16 Aug, 2018 1 commit
  21. 03 Aug, 2018 2 commits
  22. 28 Jul, 2018 1 commit
    • Greg Spencer's avatar
      Fix the gradle templates so that they default to values rather than throw... · e262817a
      Greg Spencer authored
      Fix the gradle templates so that they default to values rather than throw build exceptions. (#19916)
      
      When creating a new project, the build fails with an error similar to:
      
      "versionCode not found. Define flutter.versionCode in the local.properties file."
      
      This puts developers in the untenable situation of having to edit a file with local paths, but being unable to check it in.
      
      This changes the templates to default to using versionCode 1 and version "1.0" if they are not defined in the local.properties file.
      
      Fixes #18983.
      e262817a
  23. 28 Jun, 2018 1 commit
  24. 22 Jun, 2018 1 commit
  25. 01 Jun, 2018 1 commit
  26. 31 May, 2018 2 commits
  27. 30 May, 2018 1 commit
    • Ralph Bergmann's avatar
      add version to pubspec.yaml (#16857) · c65e9d19
      Ralph Bergmann authored
      Uses the `version` property from the `pubspec.yaml` file to set the corresponding fields in the `local.properties` file respectively in the `Generated.xcconfig` file.
      
      The `--build-name` and `--build-number` options have changed. Now they trump the `version` property from the `pubspec.yaml` file.
      
      If the `version` property is not set and the  `--build-name` and `--build-number` options are not provided, the build command will not change the `local.properties` / `Generated.xcconfig` file.
      c65e9d19
  28. 28 May, 2018 4 commits
  29. 08 Jan, 2018 2 commits