2022-10-21 leiningen | Clojure Slack Archive

leiningen

souenzzo 2022-10-21T19:46:40.169759Z

how do I get my "prod classpath" in lein? I'm using :test-paths ["test"] and when I run lein classpath it includes my test dir. This is not what I expect.

souenzzo 2022-10-21T19:48:41.698039Z

Update: even without :test-paths ["test"], with a almost empy project.clj, it includes test in my lein classpath

vemv 2022-10-21T20:15:03.696209Z

lein with-profile -user,-dev,-test classpath ?

vemv 2022-10-21T20:15:42.580879Z

(I haven't tried it) I thiiiink the classpath command had some oddities that would make it still include stuff that shouldn't

souenzzo 2022-10-21T20:16:23.463159Z

I would like to get "the classpath that will be used to create the uberjar"

souenzzo 2022-10-21T20:16:38.247709Z

mostly for debug

vemv 2022-10-21T20:19:44.812229Z

you could also add +uberjar to the mix (although it's quite rare to add deps only in the :uberjar profile)

vemv 2022-10-21T20:19:56.654529Z

LMK if that command worked for you

souenzzo 2022-10-21T21:14:16.980759Z

lein show-profiles shows every profile in the project After a lein with-profiles -auth,-base,-checkout,-debug,-default,-leiningen/default,-leiningen/test,-offline,-uberjar,-update,-user classpath | tr ':' '\n' | head (removing all profiles) it still prints "test" directory 😞

vemv 2022-10-21T23:48:34.120969Z

yeah https://github.com/technomancy/leiningen/blob/24fb93936133bd7fc30c393c127e9e69bb5f2392/leiningen-core/src/leiningen/core/classpath.clj#L592-L604

vemv 2022-10-21T23:49:34.437279Z

...it's hardcoded. you can have a profile named blank-test-paths that does a :test-paths ^:replace []

2022-10-21T20:33:42.437989Z

Is it correct to assume that if I have specified a version for a dependency defined in project.clj and multiple versions installed in ~/.m2 lein should pick the version I have specified? I ask because people on my team, myself included, have seen that installing a newer version of clojure.java-time in a project that depends on an earlier version ends up using the newer one (which is incompatible in our case).

2022-10-24T23:01:06.481379Z

This ended up being different behavior between java versions.

vemv 2022-10-25T04:29:58.971759Z

really? I would say the JVM version doesn't affect maven dependency resolution

2022-10-25T16:06:54.705929Z

It wasn't a dependency at all in the end, but changes in the resolution of the timestamps.

vemv 2022-10-25T16:26:00.445329Z

got it, yeah it has bitten me before I would use JDK8 while my team / app JDK16 so I would get some surprising behavior :)

souenzzo 2022-10-21T21:57:53.519659Z

you can start a REPL and run this code

(for [i ["java_time/api.clj"
         "java_time/api.class"
         "java_time/api.cljc"]
      f (enumeration-seq
          (.getResources
            (.getContextClassLoader (Thread/currentThread))
            i))]
  (str f))

It should result in a list with 1 single element that starts with jar:file, and contains the java-time version

2022-10-21T23:07:02.923689Z

@souenzzo thanks, it shows what I would expect, so I'll need to dig in deeper to understand what exactly is going on.

vemv 2022-10-21T23:51:59.432979Z

lein deps :tree can help you in two ways: • show which other dep might be depending on the different clojure.java-time version • explictly inform you of such ambiguities (you can always ban them by setting :pedantic? :abort in your project I consider :pedantic? a basic tenet of a nicely maintained project :)

Clojurians Log v2

leiningen