Replies: 2 comments 2 replies
-
|
Hi. The plugin only supports the basic notation: “groupId:artifactId:version”. The [versions] tag on the libs.versions.toml file or the versionRef on the settings.gradle.kts are not supported yet. It will be implemented as part of this issue. This missing feature is not urgent in my opinion, because given that you are automating all the dependencies upgrades, you don't need to define variables for your versions. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
You need to use this format:
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the bug
Hi... I would really like to use this plugin for several applications I'm working on. However, it seems to not be picking up any dependencies from a
settings.gradle.kts. Not sure why as it is explicitly listed as supported, and I have plenty of things in my version catalogs.Brief snippet from my
settings.gradle.ktsHowever, when i run
./gradlew listDependenciesI see the followingTo Reproduce
Steps to reproduce the behavior:
have version catalog in gradle settings file
Expected behavior
This should list all dependencies that exist in the settings version catalogs
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Beta Was this translation helpful? Give feedback.
All reactions