[Bug]: unneeded dependencies pulled about datahike HOT 7 CLOSED

The latest release https://github.com/replikativ/datahike/releases/tag/0.6.1549 has the clojurescript-dependency removed. @rome-user

from datahike.

Thanks for taking the time to point this out. @TimoKramer @jsmassa are you aware of a way to handle this with deps? I think we discussed it at some point.

from datahike.

with deps we have to use aliases and @jsmassa was already starting to take things apart but the PRs stalled. we have to go through all the replikativ-libs to resolve this issue.

from datahike.

Although this is manual work, I think deps.edn lets you create a pom.xml file. Then you can edit the scope of dependencies in there. The downside is that you now have to maintain two sets of dependencies: those declared in deps.edn and those declared in pom.xml

from datahike.

Editing pom.xml files separately is really not ideal. Aliases seem to be the official way https://clojureverse.org/t/how-to-provide-a-dependency-scope-in-tools-deps/1862. But I guess there are problems for downstream users with this approach, I don't know how Maven users would do this for instance(?) We can also fix any of the other replikativ libs.

@rome-user I agree that Datahike should be as lean as possible and it actually does not require more than JDK, Clojure and core.async, some serialization libs + replikativ libs atm. Are you running in specific obstacles?

from datahike.

No specific obstacles besides uberjars being very large (as they will inevitably bundle CLJS and related libraries), and the dependency tree having a lot of conflicts.

from datahike.

using exclusions for now

from datahike.