1. 21 Aug, 2022 1 commit
  2. 02 May, 2022 1 commit
  3. 28 Apr, 2022 1 commit
  4. 26 Apr, 2022 1 commit
  5. 31 Mar, 2022 1 commit
  6. 28 Mar, 2022 2 commits
  7. 19 Feb, 2022 1 commit
  8. 18 Feb, 2022 1 commit
  9. 29 Jan, 2022 1 commit
  10. 19 May, 2021 1 commit
  11. 12 Apr, 2021 1 commit
  12. 02 Apr, 2021 1 commit
  13. 10 Mar, 2021 1 commit
  14. 08 Mar, 2021 1 commit
  15. 02 Feb, 2021 1 commit
  16. 27 Jan, 2021 1 commit
  17. 22 Jan, 2021 1 commit
  18. 21 Jan, 2021 1 commit
  19. 16 Nov, 2020 1 commit
  20. 17 Sep, 2020 1 commit
  21. 16 Jul, 2020 1 commit
    • Jonah Williams's avatar
      [flutter_tools] add feature for iOS, android, and fuchsia (#61481) · 859fce90
      Jonah Williams authored
      Add feature flags for android, ios, and fuchsia (on by default). After updating the g3 rollers, the fuchsia feature will be turned off by default. Creates a simpler base type of feature flags for g3 to extend.
      
      Updates android, ios, fuchsia workflows to use feature flags check.
      Removes concept of stable artifacts and checks on flutter version.
      
      Fixes #58999
      #52859
      #12768
      859fce90
  22. 11 Jul, 2020 1 commit
  23. 23 Jun, 2020 1 commit
  24. 06 May, 2020 1 commit
  25. 06 Jan, 2020 1 commit
  26. 04 Dec, 2019 1 commit
  27. 03 Dec, 2019 4 commits
  28. 27 Nov, 2019 1 commit
    • Ian Hickson's avatar
      License update (#45373) · 449f4a66
      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
      449f4a66
  29. 24 Nov, 2019 1 commit
  30. 30 Oct, 2019 1 commit
    • stuartmorgan's avatar
      Split desktop config fallback variable by platform (#43758) · f6f6e86e
      stuartmorgan authored
      The environment variable for all desktop platforms is currently
      ENABLE_FLUTTER_DESKTOP to allow backward compatibility with existing
      workflows. However, this is actually causing issues since 'flutter
      config' provides a better experience (most importantly, IDEs will work
      correctly, which is generally not the case with the environemnt
      variable). Currently people following old (third-patry) instructions
      don't realize that they are missing available functionality, so aren't
      looking for the current instructions.
      
      In adddition, this will be confusing as different platform graduate to
      channels other than master at different times.
      
      To resolve both issues, the environment variable fallback is now
      separate for each desktop platform, and follows a naming scheme
      consistent with the web environment variable.
      f6f6e86e
  31. 24 Sep, 2019 1 commit
  32. 23 Sep, 2019 1 commit
  33. 20 Sep, 2019 1 commit
  34. 26 Jul, 2019 1 commit
  35. 25 Jul, 2019 1 commit
  36. 23 Jul, 2019 1 commit
    • 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