From slack: > to take a recent example, we forked tools namespace, applied a patch, and deployed to clojars as "juxt.forks/tns"
Currently tools.deps supports classpath-based overriding, but a user would like to override a lib with another lib to pull in a different artifact, not just a different-versioned artifact. We should consider the ability to override at the lib-level, not just at the classpath level.
This would make it very easy to e.g. use JitPack.io to use artifacts with custom patches on top (e.g. blocking bug fixes that haven't been released or merged yet).
Minor
From slack:
> to take a recent example, we forked tools namespace, applied a patch, and deployed to clojars as "juxt.forks/tns"
Currently tools.deps supports classpath-based overriding, but a user would like to override a lib with another lib to pull in a different artifact, not just a different-versioned artifact. We should consider the ability to override at the lib-level, not just at the classpath level.
This is similar to the maven relocation issue https://clojure.atlassian.net/browse/TDEPS-8#icft=TDEPS-8