-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for aliases/alternative create-basis
#32
Comments
hi, if I understood it, in theory you should be able to do that (use any aliases in a custom But there are some corner cases with maven I wasn't able to solve yet. Specifically, if one of your dependencies uses version ranges, sometime maven hits the network. I remember in clojure-lsp, maven insisted on downloading a dependency even if it was excluded: The solution was hacky, I added a file to the maven cache, so maven thought that the dependency was there: Can you share the problematic dependency to check if it's the same issue? I'd like to have a proper solution for this case, but unfortunately I didn't have too much time to work on One last question, are you sure that https://github.com/bevuta/clojure-nix-locker will work on your case? My understanding is that |
This might be possible today, but I have yet to figure it out how it would be doable:
I want to build 2 uberjars from my application code.
deps.edn
with no aliaes whatsoever.:test
and:dev
aliases from scratch.Use-case 1. works perfectly.
For 2. I tried defining a custom
buildCommand
with abuild.clj
that callscreate-basis
with the necessary aliases.This didn't work as it tried resolving the maven dependency ranges during sandboxed build-time (network calls).
https://github.com/clojure/tools.deps.alpha/blob/master/src/main/clojure/clojure/tools/deps/alpha/extensions/maven.clj#L79-L80
From a preliminary look https://github.com/bevuta/clojure-nix-locker seems to be able to solve this problem using it's design, but I much prefer clj-nix conceptually and don't want to switch away for this reason.
Is this a solveable problem using the current lock-file layout?
The text was updated successfully, but these errors were encountered: