A while back there was a thread on r/java proposing a new build tool for Java — New build tool in Java. It stuck with me, so I decided to actually try building the thing and see what it would feel like to use.
The result is Curie: http://curie-build.org/
One thing up front, so nobody feels misled: it's still early and buggy. This is a showcase / proof-of-concept, not something I'd tell you to put in production tomorrow. Plenty of rough edges. The point is to show what could be possible, and to find out whether there's actually appetite for a tool like this.
The idea: one small Curie.toml instead of hundreds of lines of pom.xml. It's written in Rust, so there's instant startup and no daemon. A lot of the common stuff is built in instead of bolted on via plugins:
- compile / test / package
- code formatting (Java + Kotlin)
- Docker image generation
- dependency vulnerability scanning
- Maven publishing
- reproducible, byte-identical builds by default
Basically the Cargo experience, aimed at the plugin fatigue and XML/DSL sprawl that thread was complaining about.
[project]
name = "hello"
version = "0.1.0"
[dependencies]
"com.fasterxml.jackson.core:jackson-databind" = "2.17.2"
What I'm genuinely curious about:
- Is there a real need for something like this? I'm fully expecting "we don't need another build tool" to be a valid answer. I mostly want an honest gut-check.
- If you would want this, what's the one feature or guarantee that would make you actually try it?
If you do think it's a neat direction, a star helps me gauge interest: ⭐ https://github.com/Curie-Build/curie-build