Gradle freezes during build, minecraft fabric 1.21.7

Hi everyone,

I’m having a problem with Gradle when trying to build a Fabric mod project.
The build always hangs at the “CONFIGURING” stage and never continues (I left it for hours).


My setup:

  • macOS 12.7 (Monterey)
  • MacBook Pro 2015 (Intel i7, 16GB RAM)
  • JDK: OpenJDK 21 (installed and working for other projects)
  • Gradle: using the project’s wrapper (./gradlew)
  • Minecraft target: 1.21.7 (Fabric modding)
  • IDE: IntelliJ IDEA (same happens from terminal)

What I already tried:

  • Deleted project’s .gradle/, build/, .idea/ multiple times
  • Deleted global Gradle cache (~/.gradle/) multiple times
  • Tried ./gradlew build --refresh-dependencies
  • Tried --no-daemon, --stacktrace, --info, --debug
  • Killed all Gradle daemons before re-running
  • Verified internet connection (downloads outside Gradle work fine)
  • Switched network to make sure it’s not a firewall issue
  • Reinstalled IntelliJ IDEA completely
  • Ran directly from terminal without IDE → same result

Errors I saw before (with --info or --debug):

Sometimes I see:
Waiting to acquire shared lock on daemon addresses registry
Lock acquired on daemon addresses registry
Releasing lock on daemon addresses registry

These lines repeat indefinitely.

Other times I also saw:
Could not resolve all files for configuration ‘:compileClasspath’.
Could not download … (dependency jars)

But after clearing caches, it usually just hangs at CONFIGURING without any new output.


Last log lines (with --debug):

[DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire shared lock on daemon addresses registry.
[DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired on daemon addresses registry.
[DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.


Has anyone else had Gradle freeze during CONFIGURING like this with Fabric + Minecraft 1.21.7?
Any suggestions on how to debug further or fix this issue?

Ignore the file lock messages, they are just normal regular work the daemon does while it is running, even if it is not running a build.

Maybe use the gradle-profiler to investigate what is happening / hanging.