Improved: Introduce a Gradle version catalog for dependency versions (OFBIZ-13487) - #1606
Conversation
…IZ-13487) Extract dependencies.gradle's ~98 version literals into gradle/libs.versions.toml. settings.gradle is untouched -- its plugin versions can't use the catalog, since Gradle evaluates that block before any catalog exists. No version changes.
84411a4 to
076d17f
Compare
|
Did you check if, with the new format, Dependabot is still producing pull requests to keep the dependencies updated or if any configuration changes are required to our GitHub actions to allow it? |
Hi @jacopoc I ran Dependabot manually for build.gradle and it produced two PRS #1610 and #1611 with the new setup as expected. I noticed there are a lot of failed PR generations from before due to GitHub's default limit of 5. Would it be wise to configure a higher limit in depandabot.yml? Also, all the open framework dependabot PRs are now stale with new changes, I'll go ahead and close them. |


Extracts dependencies.gradle's ~98 scattered dependency-version literals into a new
gradle/libs.versions.toml Gradle version catalog, with zero change in resolved
dependency versions -- verified via an empty before/after dependency-tree diff and a
full build + test run. Plugin-local dependencies (e.g. plugins/ldap) are untouched;
the catalog covers only core-framework/shared dependencies. settings.gradle is also
untouched: its two plugin versions can't use the catalog, since Gradle evaluates that
file's plugins {} block before any version catalog exists (gradle/gradle#24876,
closed not-planned).