Iqbal Ahmed
03/02/2022, 5:34 AMPaul Woitaschek
03/02/2022, 5:35 AMVampire
03/02/2022, 8:44 AMext is basically almost always the wrong answer, no matter the question. Every time you even think about using ext, you should feel dirty and make it properly instead. ๐Iqbal Ahmed
03/02/2022, 9:33 AMbuildSrc for dependencies, but updating library still is an issue. only reason I see to using ext is you can easily know the new version available and AS recognize in module setting. but still donโt want to use ext ๐Paul Woitaschek
03/02/2022, 9:35 AMThe version catalog is the standard way to goReally, this โ๏ธ
Iqbal Ahmed
03/02/2022, 9:36 AMPaul Woitaschek
03/02/2022, 9:37 AMPaul Woitaschek
03/02/2022, 9:37 AMPaul Woitaschek
03/02/2022, 9:38 AMVampire
03/02/2022, 9:39 AMbuildSrc or in a local variable, or in an ext property, or in a version catalog, doesn't really make a difference, does it?
You increase the version and are good.
And you can use some tool like renovate or dependabot or whatever that does the version increases for you,
or you can also simply use some plugin that tells you what is out dated like the Gradle Versions plugin of Ben Manes which I usually prefer.ade
03/03/2022, 8:49 AMVampire
03/03/2022, 10:03 AMbuildSrc nor version catalogs are supported:
https://www.jetbrains.com/help/idea/package-search-build-system-support-limitations.html#gradle_support
But according to https://youtrack.jetbrains.com/issue/IDEA-277582#focus=Comments-27-5173902.0-0 they should be working on supporting it now that version catalogs became stable.