We’re launching Lyria 3.5 in Google Flow Music, with advances across musicality, lyrics, vocals, and creative control
deepmind.google·6d ago
AI Engineering
Lobsters·29d ago·5 min read
The (Petty) Reason We Didn't End Up Using jj
TL;DR
A team attempted to adopt the Jujutsu (jj) version control system to replace Git in their workflow. However, they encountered issues due to Gradle's reliance on specific line endings for its wrapper script on Windows.
✦ Why It Matters
Ensure your project's line endings are compatible with the tools you plan to use, like jj and Gradle.
Key Takeaways
- Check line endings in your Gradle projects before switching version control systems.
- Use .gitattributes to enforce line-ending normalization.
- Test new tools in a controlled environment before full adoption.
- Document compatibility issues to help future team members.
Full Summary
Jujutsu (jj) is a Git-compatible version control system that simplifies commit management by eliminating the staging area and allowing for easy history rewriting. An engineer attempted to adopt jj for daily use within a Gradle project, which typically includes a Gradle Wrapper script named gradlew.bat.
This script relies on specific line endings to execute properly on Windows, necessitating CRLF line endings. However, jj's handling of files led to LF-only line endings, causing the script to malfunction.
The issue was identified as a minor detail but could significantly impact many teams in the JVM ecosystem. This experience underscores the importance of understanding file handling nuances when integrating new tools into existing workflows.
Engineers should be aware of such compatibility issues when considering jj for their projects.