Plugins can't add dependencies on custom maven repositories #9881
Labels
p: tooling
Affects the flutter_plugin_tools package
package
flutter/packages repository. See also p: labels.
Milestone
Steps to Reproduce
Right now the image_picker plugin has a dependency on the Android Image Picker Android library, which lives on GitHub along with the helper library Glide. Pulling in these libraries requires using Jitpack, which is a package repository that proxies requests to GIt. The codelab currently has a step where developers enable Jitpack by adding the following to their build.gradle:
It would be nice if the plugins could know that they depend on the Jitpack repo and add this dependency automatically. Relatedly on iOS, perhaps plugins could add dependencies on third-party Cocoapods spec repos as well.
The downside of fixing this limitation is that it would make it less predictable for the Flutter developer where all their code is coming from. So maybe this is "working as intended"? But if they're using plugins they're already depending on pub to make builds. It certainly would be nice if developers could get things done with plugins without having to make build.gradle edits.
Somewhat lower priority in that this could probably be fixed in a way that isn't a breaking API change.
/cc @mravn-google @mit-mit @jakobr-google @szakarias
The text was updated successfully, but these errors were encountered: