I seem to be having an issue with lein including some unwanted dependencies into my classpath. For example, in my project.clj I’ve got :source-paths set to ["src"] and lein classpath includes my test directory in there. My test profile does have :source-paths as ["src" "test"], but even a lein with-profile -test classpath I’m still seeing the test directory in the classpath. Any ideas why this might be happening?

@colindresj do you have it in your :dev profile as well?

Really, do you have it coming from any of these other default profiles [:base :system :user :provided :dev] mentioned in https://github.com/technomancy/leiningen/blob/master/doc/PROFILES.md#default-profiles

I don’t have it in :dev or :user, and haven’t specified any of the others

Even doing lein with-profile -base,-system,-user,-provided,-dev classpath | tr ":" "\n" gives me something I don’t expect (including my test dir still being there)

Just asked a coworker to do the same and it’s happening for him as well

@colindresj just for completeness, perhaps make a profile, called :trial like

:trial {:source-paths ^:replace ["src"]}

Here’s the first couple lines of my output @mikerod

@colindresj that’s with doing a profile like I mentioned above?

Yep

interesting, makes me think that classpath ignores the given profiles

I’d have to look at that a bit closer, doesn’t seem ideal

Yeah

That’s possible

I actually ran into this because a different tool is using the output of lein classpath and I was getting some weird results, so I started digging

Basically end up in this

(defn get-classpath
  "Return the classpath for project as a list of strings."
  [project]
  (for [path (concat (:test-paths project)
                     (:source-paths project)
                     (:resource-paths project)
                     [(:compile-path project)]
                     (checkout-deps-paths project)
                     (for [dep (resolve-managed-dependencies
                                :dependencies :managed-dependencies project)]
                       (.getAbsolutePath dep)))
        :when path]
    (normalize-path (:root project) path)))

Looks like it will include :test-paths too

maybe that is your problem

maybe you have :test-paths at the root of the project.clj

Let me check

if you make a profile like :trial and put :test-paths ^:replace [] I think, that may help

Still may have to consider if you are using lein checkouts too though, since those may interfere as well

I think this impl does respect chosen profiles though

Replacing :test-paths fixes it for me

🎉

I don’t have :test-paths set in this project.clj, but I also have checkouts, so I’ll look through those

ah yeah

You may be able to squash checkouts with :checkout-deps-shares ^:replace [] in a profile too , but I’d have to experiment with that

I don’t know that is the correct thing at all, just off-the-head

Not able to experiment mysefl at the moment

That gives me a much smaller classpath, but still have test in there with :checkout-deps-shares ^:replace []

Maybe it’s a plugin that’s doing something with :test-paths?

Either way, I’m good for now just replacing :test-paths on a particular profile. Thanks @mikerod

Yeah. Hard to say I guess

Similar topics have came up in here recently

Seems like a few lein built in tasks would be nicer if they could give you a classpath/deps tree etc that is representative of the “production build”

Without manually tryin to fight off dev/test things getting in it.

Yeah for sure

TODO hah

I’ve found using lein-cprint or lein-pprint really helpful debugging stuff like the above - you can do lein cprint :checkout-deps-shares to see the default, or lein with-profile uberjar cprint :checkout-deps-shares, etc.

@greg316 agreed that that can be a helpful tool

thanks for reminding me of passing keywords to it

Ah, very helpful @greg316

Thanks