This project has given up GitHub. (See Software Freedom Conservancy's Give Up GitHub site for details.)
You can now find this project at paste.rossabaker.com instead.
Any use of this project's code by GitHub Copilot, past or present, is done without our permission. We do not consent to GitHub's use of this project's code in Copilot.
Join us; you can give up GitHub too! Ready to make the change? Have a look at the convenience script.
sbt doesn't resolve library conflicts across Ivy configurations. If a compile-scoped jar depends on log4j-1.2.12, and a runtime-scoped jar depends on log4j-1.2.14, both end up on sbt's runtime classpath and in the jar. The above lets Ivy resolve the conflicts in a more Maven-like fashion, at the expense of a bloated lib_managed (each jar is copied into each child configuration).
Is there a better way?