Skip to content

Define Gradle version catalog inspection approach#22

Merged
JuanTorchia merged 1 commit into
masterfrom
feature/gradle-version-catalog-research
Apr 23, 2026
Merged

Define Gradle version catalog inspection approach#22
JuanTorchia merged 1 commit into
masterfrom
feature/gradle-version-catalog-research

Conversation

@JuanTorchia

Copy link
Copy Markdown
Owner

Summary

  • Add a design note for read-only Gradle version catalog inspection without executing Gradle.
  • Define the MVP scope: conventional gradle/libs.versions.toml, TOML parsing, alias normalization, dependency/plugin alias resolution, and bundle expansion.
  • Document out-of-scope areas: custom catalogs, convention plugins, dynamic aliases, conflict resolution, and effective version calculation.
  • Link the proposal from the rule contribution guide.

Validation

  • python -B scripts/check-local-markdown-links.py
  • Legacy documentation path search returns only the historical rename note in docs/engineering-log/012-public-repository-readiness.md.
  • Public documentation hygiene search returns no workstation-specific paths or private planning references.
  • git diff --check
  • mvn clean test '-Dmaven.compiler.release=22'

Closes #5.

@JuanTorchia JuanTorchia marked this pull request as ready for review April 23, 2026 04:01
@JuanTorchia JuanTorchia merged commit 636eafb into master Apr 23, 2026
2 checks passed
@JuanTorchia JuanTorchia deleted the feature/gradle-version-catalog-research branch April 23, 2026 04:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Improve Gradle version catalog detection research spike

1 participant