Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider raising minimum supported Gradle version to 8 #2004

Closed
6 tasks
ciscoo opened this issue Jan 16, 2024 · 1 comment
Closed
6 tasks

Consider raising minimum supported Gradle version to 8 #2004

ciscoo opened this issue Jan 16, 2024 · 1 comment

Comments

@ciscoo
Copy link

ciscoo commented Jan 16, 2024

If you are submitting a bug, please include the following:

  • summary of problem
  • Gradle or Maven version
  • spotless version
  • operating system and version
  • copy-paste your full Spotless configuration block(s), and a link to a public git repo that reproduces the problem if possible
  • copy-paste the full content of any console errors emitted by gradlew spotless[Apply/Check] --stacktrace

If you're just submitting a feature request or question, no need for the above.


The current required minimum Gradle 6.1.1 which was released nearly 4 years ago: https://docs.gradle.org/6.1.1/release-notes.html

I think its time to raise the minimum to a supported version of Gradle. By supported, I mean the Gradle team has a milestone for it: https://github.com/gradle/gradle/milestones

There exists a milestone for Gradle 7, but there have been several release of 8 already, I suggest going for the latest.

I'm not familiar with Spotless' codebase, but I would think this would reduce some technical debt due to maintaining support for legacy versions of Gradle. And of course take advantage of any new things.

@nedtwigg
Copy link
Member

The only technical debt around Gradle that I am aware of is

which is not related to supporting old versions of Gradle. I'd happily bump minimum to 8 if it provided anything, and I'm happy to reopen if someone finds something where our thorough back-compat is holding us back.

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

No branches or pull requests

2 participants