yeah I would really like to explore tools.deps.alpha a bit more, expecially the resolver part

one day...

@alexmiller Can you think of a case where clj on a deps.edn file wouldn't resolve a dependency that tools.deps.alpha would resolve against a deps.edn file? In particular, https://github.com/juxt/pack.alpha/issues/7#issue-321346647 something is going off to another repo. pack only considers the deps.edn, and doesn't merge the system one. For some reason it works if I add maven central, but what does that have to do with glassfish?

the install deps.edn includes the central and clojars maven repos

https://github.com/clojure/brew-install/blob/1.9.0/src/main/resources/deps.edn

other than that, shouldn’t be any different

@alexmiller I guess another way of describing this would be: - I run clj against a deps.edn file - so everything should end up in .m2 - I run tools.deps.alpha against the same deps.edn and it fails as more needing more resolving

doesn’t make sense to me

If I add the :mvn/repos to deps.edn, somehow it allows it to fetch from glassfish repo

ah, they commented https://github.com/juxt/pack.alpha/issues/7#issuecomment-387732402

I'm not really sure what is going on here, and why this either needs to run every time (uncacheable) or doesn't get picked up by clj

I guess because once it’s in central they want you to get it from there?

dunno, weird

yeah, real weird.

This definitely highlights that I need a good way to do -Srepro without the local deps.edn file ever being picked up though 😉

Or rather, I need a way to pick up only the system deps.edn