-
Notifications
You must be signed in to change notification settings - Fork 30.5k
[packages] Consider updating legacy_project to Kotlin Gradle #184656
Copy link
Copy link
Open
Labels
P2Important issues not at the top of the work listImportant issues not at the top of the work listpackageflutter/packages repository. See also p: labels.flutter/packages repository. See also p: labels.platform-androidAndroid applications specificallyAndroid applications specificallyteam-androidOwned by Android platform teamOwned by Android platform teamtriaged-androidTriaged by Android platform teamTriaged by Android platform team
Metadata
Metadata
Assignees
Labels
P2Important issues not at the top of the work listImportant issues not at the top of the work listpackageflutter/packages repository. See also p: labels.flutter/packages repository. See also p: labels.platform-androidAndroid applications specificallyAndroid applications specificallyteam-androidOwned by Android platform teamOwned by Android platform teamtriaged-androidTriaged by Android platform teamTriaged by Android platform team
Type
Fields
Give feedbackNo fields configured for issues without a type.
The
legacy_projectapp—which is used to help ensure that plugins still build with old, minimally-updated projects that existing in the wild—is now the only use of Groovy in the repository. Since my understanding is that we don't expect any compat issues related to using Kotlin vs Groovy for plugin files, we may want to consider updating those files to Kotlin Gradle (without modernizing their contents beyond that), so that we don't need to continue to deal with Groovy in one obscure place.On the other hand, old real-world apps are almost certainly still using Groovy, so if we think it's better to err on the side of minimal changes here, as we usually do for this test app, we may want to leave it as-is.