JLBP-16 Recommend using Gradle version catalogs

Open
#2,471 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Quiet
Tech stack
java
Domain
build-system

Research direction

Start with the root project’s Gradle configuration and the guidance in JLBP-16. Replace the recommended root-project ext dependency version declarations with Gradle version catalogs, then verify that dependency versions remain available across the build and are compatible with Gradle Isolated Projects.

Written by the indexing model from the issue text.

Description

The recommended ext extension in root project for Gradle in https://jlbp.dev/JLBP-16 is bad practice nowadays (cross project configuration), and won't work with Gradle's Isolated Projects feature.

Gradle has had a Version Catalog feature for some time now specifically to declare dependency versions to be used across the build.

Dominant language
Java
Stars
163
Forks
81
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from GoogleCloudPlatform/cloud-opensource-java

All issues in GoogleCloudPlatform/cloud-opensource-java

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.