Can't build Zilla offline due to JitPack-based K3PO dependencies

[thealmikey]

Hey Zilla team 👋,

I’ve been playing around with Zilla lately and wanted to explore the internals and features a bit deeper (really exciting stuff, btw!). I tried building the project locally — especially in offline or limited-connectivity environments — but hit a snag with resolving dependencies from JitPack.

The main blocker seems to be that several io.aklivity.k3po dependencies (like driver, lang, control-junit, k3po-maven-plugin, etc.) resolve via JitPack under rewritten groupIds, e.g.:

com.github.aklivity.k3po:lang:-<commit>-1
This makes it difficult to build or mirror Zilla dependencies offline without rewriting the whole project’s dependency tree or publishing those modules to a more canonical repository (e.g., Maven Central or GitHub Packages with stable coordinates).

Would love to be able to:

Build Zilla completely offline after one online fetch.

Reference a stable version of K3PO that doesn’t depend on JitPack rewrites.

Is there any plan to publish K3PO artifacts under io.aklivity.k3po to a more standard repo? Or perhaps offer a BOM or snapshot repo that aligns better with Maven expectations?

Thanks again for the amazing work
— a curious tinkerer

[thealmikey]

Quick update—I was able to get Zilla building on my setup. It turned out I needed to have Docker Engine running on my Windows 10 machine, and after commenting out the Maven Enforcer plugin, things went smoothly. I’ll go ahead and close this issue.