>
> If a version of some dependency is already on the classpath (either has
> been there from the start, or was previously added via pomegranate),
> results are undefined if a different version of the same dependency is
> later added via pomegranate. Sometimes you get lucky and nothing bad
> happe
On Dec 4, 2012, at 2:52 AM, Laurent PETIT wrote:
> 2012/12/4 rob :
>> That was my first thought, and considered also generating a project.clj, but
>> after thinking about it I decided I didn't want to encourage this type of
>> behavior beyond REPL experimentation, so I preferred to do it in a way
2012/12/4 rob :
> That was my first thought, and considered also generating a project.clj, but
> after thinking about it I decided I didn't want to encourage this type of
> behavior beyond REPL experimentation, so I preferred to do it in a way that
> focuses on the REPL.
Hi,
Really appreciate tha
That was my first thought, and considered also generating a project.clj,
but after thinking about it I decided I didn't want to encourage this type
of behavior beyond REPL experimentation, so I preferred to do it in a way
that focuses on the REPL.
On Tuesday, December 4, 2012 2:24:38 AM UTC-5,
Hi,
may I suggest a different solution? Create a meta project, which just
depends on all the contrib libraries and specify this as a dependency in
your project. In other parts of the world this is called a "BOM" - a bill
of material.
Kind regards
Meikel
--
You received this message because y
John Aspden posted an interesting question on Stack Overflow about adding
all of the latest versions of contrib libraries as dependencies in a REPL
session. The question and my response can be found here:
http://stackoverflow.com/questions/13673094/how-do-i-depend-on-every-clojure-contrib-library/
