leiningen

2022-04-13T20:43:10.572309Z

i realize that it's helpful for repl-driven development for :dev to be in the default profile, but it seems weird to me that :test also gets access to :dev. I just ran into an issue where my code runs with lein repl and lein test, but fails with lein uberjar because i had accidentally required one of my dev namespaces in my core code

2022-04-13T20:44:28.706689Z

is there a way to enforce that the test task only runs with the :test profile? outside of lein with-profile test test of course. i'd like to enforce this across my team

2022-04-14T13:29:12.620489Z

oh yeah, i can subtract! forgot about that. thanks, i'll add that

vemv 2022-04-14T06:25:05.331129Z

I use lein with-profile -dev test The enforcement is that it runs on CI. Once you get used to some or other incantation, using bare lein test will feel just wrong

2022-04-13T23:48:53.713999Z

would lein check have caught this? I suspect it would have. I often use it because it runs quickly and finds "low hanging fruit" errors that are easier to fix the sooner you find them