The (Petty) Reason We Didn't End Up Using jj
Summary
Gradle explains why it didn’t adopt the Jujutsu (jj) VCS for Gradle projects, centering on a seemingly small but impactful line-ending issue around gradlew.bat and .gitattributes. The post details the workaround using git worktree and the potential fix via proper CRLF handling, and notes they’ll revisit jj if eol support lands. It serves as a practical case study of how cross-platform tooling constraints can influence tool choice in JVM ecosystems.