Closed vnickolov closed 1 month ago
I figured it out, after reading the code 🙇
Declaring the additional catalog results in an additional Gradle task with the name of the catalog (capitalised) as a suffix, in the above case I had to do this in order for it to work
./gradlew versionCatalogUpdateAdditionalCatalog --interactive
Went back to the docs, and I clearly missed that paragraph 🤦
Hello,
I have two separate version catalog files - one is the default and the other one is named, they are both used and declared in
settings.gradle
, all looks good there.Then I specify the additional catalog
Intentionally lowered a version declared there. When I run
The "offending" version has been reported by the
versions
plugin but I don't see theopen/gradle/additional.versions.toml
being updated, nor there isopen/gradle/additional.versions.updates.toml
generated.What am I missing? Is this a bug, or I have something misconfigured?
Thank you in advance, Ves