Skip to content

port gradle logic to java or kotlin #19625

Closed

Description

@Hixie

Apparently using "groovy" is no longer cool (it uses reflection or something), and we should move to Java or Kotlin for our gradle scripts.

Activity

  1. added
    toolAffects the "flutter" command-line tool. See also t: labels.
    c: performanceRelates to speed or footprint issues (see "perf:" labels)
    t: gradle"flutter build" and "flutter run" on Android
    on Jul 20, 2018
  2. added this to the milestone on Jul 20, 2018
  3. jonahwilliams commented on Feb 5, 2020

    @jonahwilliams
    Contributor

    I don't think we would plan to do this one ourselves, but I would certainly review/welcome patches from people who felt more strongly about it.

  4. jonahwilliams commented on Feb 5, 2020

    @jonahwilliams
    Contributor
  5. added
    P2Important issues not at the top of the work list
    on May 29, 2020
  6. removed this from the milestone on Aug 17, 2020
  7. blasten commented on May 7, 2021

    @blasten

    This has been suggested by the AGP team too. They built AGP in Kotlin

  8. stuartmorgan-g commented on Sep 1, 2022

    @stuartmorgan-g
    Contributor

    Another reason to switch to Kotlin would be to reduce the number of languages that developers have to interact with when using Flutter. The default app and plugin templates have been using Kotlin for a while, so changing the gradle files in the template to Kotlin would reduce the language set for Android development from {Dart, Kotlin, Groovy} to {Dart, Kotlin}.

    (We'd need to update all the docs about gradle files to show both though.)

  9. reidbaker commented on Feb 27, 2023

    @reidbaker
    Contributor

    Closing this as a dup of #121541 since that bug is a bit better in clarity and scope.

  10. github-actions commented on Mar 13, 2023

    @github-actions

    This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

  11. locked as resolved and limited conversation to collaborators on Mar 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Important issues not at the top of the work listc: new featureNothing broken; request for a new capabilityc: performanceRelates to speed or footprint issues (see "perf:" labels)t: gradle"flutter build" and "flutter run" on AndroidtoolAffects the "flutter" command-line tool. See also t: labels.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions