JMH Visualizer 1.1.0 & Related Gradle Plugin Released
r/gradle • u/Crazy-Wrongdoer-4904 • 12d ago
so i have this cool mc zip and ive been trying to use gradle to compile it into a jar and all i keep getting is errors pls someone help/do it for me
r/gradle • u/Party_Till_I_Die • 15d ago
r/gradle • u/EliSoli • 23d ago
r/gradle • u/Party_Till_I_Die • Sep 25 '26
https://docs.gradle.org/9.8.0/release-notes.html
Bug fixes andā¦
ā Java 27 support
šŖMaven mirror settings reuse
š Linked problem locations in build output
Please report any š on GitHub!
r/gradle • u/SessionBytes • Sep 22 '26
The latest Gradle release candidate brings several useful updates for Java developers ā and the biggest one is Java 27 support. āļø
Whatās new?
š¹ Java 27 support for Gradle daemon & toolchains
š¹ Reuse Maven mirror settings
š¹ Up to 45% faster builds on affected Windows systems
š¹ Lazy destinationDirectory for Copy & Sync tasks
š¹ Smarter Maven POM generation with up-to-date checks
š¹ Improved build error and problem reporting
š¹ Better Groovydoc support for modern Java syntax
For developers moving toward Java 27, Gradle 9.8 is an important update to watch.
Java 27 + Gradle 9.8 = modern Java builds getting better. š
#Java #Java27 #Gradle #SpringBoot #JavaDeveloper #BackendDevelopment #SoftwareDevelopment #Programming #DevTools #BuildTools #Developer #TechUpdates #SessionBytes
r/gradle • u/[deleted] • Sep 17 '26
Had one of those moments where a build that worked fine yesterday suddenly started complaining today.
ā
āWhen that happens, what's usually the first thing you check?
r/gradle • u/No_Gate9933 • Sep 17 '26
I've mostly stuck with the standard tasks and only added custom ones when I really needed them .
Curious how common custom task are in other people,s projects.Do you use them often ?
r/gradle • u/jaavaaguru • Sep 16 '26
Iāve been working on a unified color theme pipeline to solve a personal headache: keeping my VS Code, Ghostty, and terminal color schemes synchronized without manually tweaking hex codes across multipleĀ settings.jsonĀ and config files.
Along the way, I ended up building a custom language, with its own Gradle plugin, and a zero-Node VSIX packaging Gradle plugin. Here is a breakdown of what was just released:
CTĀ is a lightweight DSL designed specifically for defining color palettes and compiling them into target theme formats (VS Code, Ghostty, iTerm2, etc.).
Color Primitives: Supports 6-digit RGB (#00FF00) and 8-digit RGBA hex colors (#00FF00FF).
Variables & Collections: Define reusable color variables and structured palettes (Palette human = { ... }).
Color Functions: Built-in methods likeĀ hsbaLerp(...)Ā andĀ brightness(...)Ā for procedural palette generation.
Template Blocks: Interpolate values directly usingĀ {{{ ... }}}Ā template blocks.
We also just added native VS Code syntax highlighting support forĀ .ctĀ files!
If you build VS Code extensions using JVM languages, you usually have to shell out toĀ npx @vscode/vsceĀ or set up Node/npm in CI.
To keep the build 100% self-contained on the JVM, I built a declarative Gradle plugin that packages VSIX extension bundles natively:
Zero Node.js /Ā vsceĀ dependency: Runs purely inside Java/Gradle.
In-Memory Manifest Generation: Automatically synthesizes and managesĀ package.json,Ā extension.vsixmanifest, and Open Packaging Conventions ([Content_Types].xml).
Built-in Lifecycle Tasks: RunĀ ./gradlew packageVsix,Ā ./gradlew installVsix, orĀ ./gradlew uninstallVsixdirectly from your terminal.
To showcase the pipeline, I created a retro CRT terminal theme pack featuring amber and green phosphor palettes on beige and heavy metal dark backgrounds.
Here is how clean theĀ build.gradleĀ file looks when combining the CT compiler and VSIX packager:
plugins {
id 'io.github.qishr.cascara-gradle-plugins.ct' version '0.1.0'
id 'io.github.qishr.cascara-gradle-plugins.vsix' version '0.2.2'
id 'base'
}
ct {
formats {
// When a configuration (e.g. 'retroAmber') for a format (e.g. ghostty)
// doesn't specify an output filename, the output filename is assembled
// based on the configuration name (e.g. 'retroAmber') changed into
// -kebab-case- and the suffix is obtained from the format definition
// (e.g. res://ghostty.tc)
ghostty {
retroAmber { entry = "retro-amber-on-bright-beige.ct"; }
retroGreen { entry = "retro-green-on-bright-beige.ct"; }
}
iterm2 {
retroAmber { entry = "retro-amber-on-bright-beige.ct"; }
retroGreen { entry = "retro-green-on-bright-beige.ct"; }
}
vscode {
retroAmberOnBrightBeige { entry = "retro-amber-on-bright-beige.ct"; }
retroAmberOnDullBeige { entry = "retro-amber-on-dull-beige.ct"; }
retroAmberOnHeavyMetal { entry = "retro-amber-on-heavy-metal.ct"; }
retroGreenOnBrightBeige { entry = "retro-green-on-bright-beige.ct"; }
retroGreenOnDullBeige { entry = "retro-green-on-dull-beige.ct"; }
retroGreenOnHeavyMetal { entry = "retro-green-on-heavy-metal.ct"; }
}
}
}
vsix {
name = "cascara-retro-theme"
displayName = "Cascara Retro Theme"
description = "Retro theme pack for Visual Studio Code"
version = project.version.toString()
publisher = "Cascara"
icon = "images/icon.png"
categories "Themes"
engines = [ "vscode": "^1.103.0" ]
readme = layout.projectDirectory.file("README.md")
license = layout.projectDirectory.file("LICENSE")
imagesDir = layout.projectDirectory.dir("src/main/resources/vscode/images")
// Automatically pulls compiled output from cascara-gradle-plugins.ct
themes.from(layout.buildDirectory.dir("themes"))
}
// Lifecycle hooks
tasks.named('packageVsix') { dependsOn compileAllCt }
tasks.named('build') { dependsOn tasks.named('packageVsix') }Would love to hear any thoughts or feedback on the VSIX packaging setup or the CT language!
r/gradle • u/TheOrangeApple3 • Sep 11 '26
Hi sorry to be a bother but i could really use some help with compiling some minecraft mods from github. Ive tried doing it but they keep throwing up erros and I just don't know how to resolve the issues even after hours of google searching (although im i completly inexpericed with these things)
https://github.com/Asek3/sodium-1.12
https://github.com/Asek3/Oculus/tree/1.12.2
https://github.com/westernbear/Oculus-1.12
any help and I would be so gratefull!!!
r/gradle • u/Party_Till_I_Die • Sep 09 '26
r/gradle • u/Party_Till_I_Die • Aug 31 '26
Today, we launched our new Gradle Security Subscription offering. And I made an infographic about it. But, because I am me, I also made a blog post about it. Choose wisely (or read both š).
r/gradle • u/confusionismyworld • Aug 29 '26
drspider@pop-os:~$ git clone https://github.com/armandoxtraceroespalda-dev/ScalableLux-Sable.git
Cloning into 'ScalableLux-Sable'...
remote: Enumerating objects: 1297, done.
remote: Counting objects: 100% (88/88), done.
remote: Compressing objects: 100% (64/64), done.
remote: Total 1297 (delta 16), reused 57 (delta 5), pack-reused 1209 (from 1)
Receiving objects: 100% (1297/1297), 483.15 KiB | 7.00 MiB/s, done.
Resolving deltas: 100% (554/554), done.
drspider@pop-os:~$ cd ScalableLux-Sable
drspider@pop-os:~/ScalableLux-Sable$ ./gradlew build
bash: ./gradlew: Permission denied
drspider@pop-os:~/ScalableLux-Sable$ chmod +x gradlew
drspider@pop-os:~/ScalableLux-Sable$ ./gradlew build
Downloading https://services.gradle.org/distributions/gradle-8.12-all.zip
.....................10%......................20%......................30%......................40%......................50%......................60%......................70%......................80%......................90%......................100%
Welcome to Gradle 8.12!
Here are the highlights of this release:
- Enhanced error and warning reporting with the Problems API
- File-system watching support on Alpine Linux
- Build and test Swift 6 libraries and apps
For more details see https://docs.gradle.org/8.12/release-notes.html
To honour the JVM settings for this build a single-use Daemon process will be forked. For more on this, please refer to https://docs.gradle.org/8.12/userguide/gradle_daemon.html#sec:disabling_the_daemon in the Gradle documentation.
Daemon will be stopped at the end of the build
[Incubating] Problems report is available at: file:///home/drspider/ScalableLux-Sable/build/reports/problems/problems-report.html
FAILURE: Build failed with an exception.
* What went wrong:
Included build '/home/drspider/FlowSched' does not exist.
* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.
Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
For more on this, please refer to https://docs.gradle.org/8.12/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.
BUILD FAILED in 24s
drspider@pop-os:~/ScalableLux-Sable$
r/gradle • u/Massive_Show_3967 • Aug 21 '26
New to build systems exploring the existing, I was happy to find out I do not have to install something only to find out I have to install it :(, -1 to gradle for giving me false hope.
r/gradle • u/Party_Till_I_Die • Aug 19 '26
https://docs.gradle.org/9.7.1/release-notes.html
Fixes regressions reported against 9.7.0.
Report new š on GitHub!
r/gradle • u/Party_Till_I_Die • Aug 19 '26
We're building a set of Gradle Agent Skills. There are five candidates below:
gradle-cli ā Run Gradle the right way. Teaches the agent correct ./gradlew invocation: which task to run, which flags matter, what's version-specific, and how to read the output. No more --stacktrace on everything and hoping.
gradle-bestpractices ā Lint your build against current conventions. Scans your build logic and flags what's off: legacy APIs, subprojects {} sprawl, misused configurations, and missing version catalogs. Points to the current recommended pattern for each finding.
gradle-init ā Bootstrap a new Gradle project. Sets up a working project from scratch: sensible defaults, version catalog, and a starter layout for KMP, Android, or Spring. Skips the hour of copy-pasting from an old repo or adding random libraries.
gradle-upgrade ā Upgrade Gradle and clear deprecations. Version-aware upgrade path: bumps the wrapper, finds deprecated usages in your build logic, and rewrites them for the target version. Handles the multi-step hops so you're not stuck three majors behind.
gradle-cc-migrate ā Make your build Configuration Cache compatible. Reads your build logic, finds what breaks the configuration cache, and refactors it ā script-level state, Project access at execution time, non-serializable task inputs. The single biggest build-speed win, minus the archaeology.
Which would help you most? Which one would you actually use? Do you have a better idea?
r/gradle • u/Party_Till_I_Die • Aug 13 '26
Until now, a single broken build script would fail the entire sync. Every script turned red and no more autocomplete.
Resilient sync fixes this. Gradle builds tooling models for every project that configured successfully and reports only the failures, so one broken convention plugin no longer takes down the other projects. You keep code completion and highlighting in the build logic you're repairing.
Write-up here: https://blog.gradle.org/resilient-sync
r/gradle • u/Party_Till_I_Die • Aug 12 '26
Small IntelliJ IDEA win for Gradle users: version catalog accessors now show their resolved coordinates inline.
r/gradle • u/Party_Till_I_Die • Aug 11 '26
Our CI bot now reads failures out of Develocity, groups them, and posts a short summary on the PR. If you want to see it in action, here's my write-up with screenshots: https://blog.gradle.org/dogfooding-failure-summaries
r/gradle • u/Party_Till_I_Die • Aug 06 '26
Isolated Projects moved from experimental to incubating in 9.7.0. With it enabled, each project in a build is isolated from the others, which lets Gradle configure them in parallel.
Some numbers from the blog post:
Gradle's own build (300 subprojects): median IDE sync 84s ā 47s
A 2,500-project Java monorepo: configuration with build-script recompilation 10m53s ā 2m59s
An Android monorepo of 5,000+ projects: Android Studio sync 5m09s ā 2m44s
Configuration Cache is a prerequisite.
You can enable it with org.gradle.isolated-projects=true in gradle.properties.
Here's the full blog post: https://blog.gradle.org/introducing-isolated-projects.
r/gradle • u/Party_Till_I_Die • Aug 06 '26
https://docs.gradle.org/9.7.0/release-notes.html
Bug fixes andā¦
š± Isolated Projects graduates to incubating
ā” Broader Configuration Cache compatibility
š More source locations in problem reports
Please report any š on GitHub!