On Jan 28, 12:09 am, Phil Hagelberg wrote:
> Perry Trolard writes:
> Any time you have dependencies that aren't in repositories, it's going
> to cause pain. It's much better to put them in a repository, even if
> it's a private/local one, than to bend Leiningen to work with bare jars.
>
> -Phil
Perry Trolard writes:
> I wasn't clear. By "development environment," I meant my `clj` script,
> not any particular project per se. In my clj script, I specify a place
> on the filesystem to drop jars that I want on the classpath when its
> invoked; I know others have setups like this. I always p
On Jan 6, 6:07 pm, Perry Trolard wrote:
> I suppose I could create a leiningen project for my clj script,
> specifying libraries I want as dependencies & then just putting its
> uberjar on the classpath, but this requires that the libraries are
> available in maven repos. Have other leiningen use
On Jan 2, 12:35 am, Phil Hagelberg wrote:
> I'm a little reluctant to make calculating the classpath any more
> complicated than it currently is since that logic needs to be duplicated
> in a few places, but I agree that the current situation is not great.
>
> Another idea would be to write a h
Perry Trolard writes:
> Currently for the Leiningen uberjar task, all dev-dependencies are
> included in the resulting standalone jar. In a comment in uberjar.clj,
> there's a note that excluding these is on the todo list. I wonder if
> there are any ideas on how best to do it?
One simple way wo
Greetings,
Currently for the Leiningen uberjar task, all dev-dependencies are
included in the resulting standalone jar. In a comment in uberjar.clj,
there's a note that excluding these is on the todo list. I wonder if
there are any ideas on how best to do it?
I tried to tackle this in a naive way
