if you have a project A that requires a project B, is it possible to only require certain libraries of project B in test/dev profiles?
we have a common library with lots of dependencies, and some of these dependencies are just used in dev/testing, but they still need to be declared in the default profile, and end up in the uberjar when you build the application depending on the library
I was wondering if there was a way, apart from maybe just creating another library for dev/test related helpers/libraries
At some workplace we used https://github.com/achin/lein-parent which can define a parent profile I believe
> I was wondering if there was a way, apart from maybe just creating another library for dev/test related helpers/libraries Seems the cleanest approach tbh!
yeah I guess I should just do that instead