Re: Wrong clojure version depending on lein dependencies (was: ANN: Clojure 1.5)

In lein 2.1 using `lein deps :tree` will print out any version ranges it finds. Hopefully this helps with when noticing similar dependency issues. On Sat, Mar 2, 2013 at 5:42 PM, Nelson Morris wrote: > On Sat, Mar 2, 2013 at 4:17 PM, Frank Siebenlist > wrote: >>> ... >>> The chain causing proble

Re: Wrong clojure version depending on lein dependencies (was: ANN: Clojure 1.5)

On 4 March 2013 15:30, Wolodja Wentland wrote: > On Mon, Mar 04, 2013 at 15:04 +0100, Michał Marczyk wrote: > >> On the other hand, if you care about securing your project, pulling in >> the latest bugfixes etc., you will need to monitor new releases >> anyway, regardless of the version numbering

Re: Wrong clojure version depending on lein dependencies (was: ANN: Clojure 1.5)

On Mon, Mar 04, 2013 at 09:54 -0500, Chas Emerick wrote: > AFAICT, the vast majority of Leiningen users (same goes for Maven users as > well) expect the dependency vector [org.clojure/clojure "1.2.0"] to establish > a > lower bound, the equivalent of "[1.2.0,)". Further, people expect the maximum

Re: Wrong clojure version depending on lein dependencies (was: ANN: Clojure 1.5)

On Mon, Mar 4, 2013 at 2:55 PM, Wolodja Wentland wrote: > On Mon, Mar 04, 2013 at 14:42 +, David Powell wrote: > > > "1.2" in this case is a "soft" dependency on 1.2. This is probably what > you > > want. > > > > > Dependency+Mediation+and+Conflict+

Re: Wrong clojure version depending on lein dependencies (was: ANN: Clojure 1.5)

On Monday, March 4, 2013 3:42:56 PM UTC+1, David Powell wrote: > > Version ranges aren't for communicating what versions of libraries you > have tested against - that is best done out-of-band. If you include a > version range, like the one above, you are saying that you want the > software to

Re: Wrong clojure version depending on lein dependencies (was: ANN: Clojure 1.5)

On Mon, Mar 04, 2013 at 14:42 +, David Powell wrote: > "1.2" in this case is a "soft" dependency on 1.2.  This is probably what you > want. > > Dependency+Mediation+and+Conflict+Resolution# > DependencyMediationandConflictResolution-DependencyVersion

Re: Wrong clojure version depending on lein dependencies (was: ANN: Clojure 1.5)

On Mar 4, 2013, at 9:01 AM, Meikel Brandmeyer (kotarak) wrote: > Hi Chas, > > Am Montag, 4. März 2013 14:33:29 UTC+1 schrieb Chas Emerick: > There are a lot of reasons for this, but #1 for me is that few people > understand the implications of version ranges, either downstream of their > publis

Re: Wrong clojure version depending on lein dependencies (was: ANN: Clojure 1.5)

On Mon, Mar 4, 2013 at 2:01 PM, Meikel Brandmeyer (kotarak) wrote: > Hi Chas, > > Am Montag, 4. März 2013 14:33:29 UTC+1 schrieb Chas Emerick: > >> There are a lot of reasons for this, but #1 for me is that few people >> understand the implications of version ranges, either downstream of their >>

Re: Wrong clojure version depending on lein dependencies (was: ANN: Clojure 1.5)

On Mon, Mar 04, 2013 at 15:04 +0100, Michał Marczyk wrote: > On the other hand, if you care about securing your project, pulling in > the latest bugfixes etc., you will need to monitor new releases > anyway, regardless of the version numbering scheme used by their > maintainers. And then release

Re: Wrong clojure version depending on lein dependencies (was: ANN: Clojure 1.5)

On Monday, March 4, 2013 3:01:13 PM UTC+1, Meikel Brandmeyer (kotarak) wrote: > > The range [1.2;1.5) means that the library was tested with 1.2 up to 1.4 > and - believing in semver - their patchlevel children. 1.5 (was at that > time) not released, yet. So compatibility couldn't be guaranteed

Re: Wrong clojure version depending on lein dependencies (was: ANN: Clojure 1.5)

On 4 March 2013 15:01, Meikel Brandmeyer (kotarak) wrote: > The range [1.2;1.5) means that the library was tested with 1.2 up to 1.4 and > - believing in semver - their patchlevel children. 1.5 (was at that time) > not released, yet. So compatibility couldn't be guaranteed. For me this is a > reas

Re: Wrong clojure version depending on lein dependencies (was: ANN: Clojure 1.5)

On Mon, Mar 04, 2013 at 06:01 -0800, Meikel Brandmeyer (kotarak) wrote: > Ok. So instead of the range I specify "[org.clojure/clojure "1.2"]". What does > that mean? Now I either excluded *all* clojure versions not= 1.2 or the > version > number doesn't mean anything. Then we should get rid of it

Re: Wrong clojure version depending on lein dependencies (was: ANN: Clojure 1.5)

On Mon, Mar 04, 2013 at 08:33 -0500, Chas Emerick wrote: > FWIW, contributors to Pomegranate and Leiningen are working on general > solutions to this sort of madness, but the use of version ranges will always > be > largely unwarranted, especially in published libraries. > There are a lot of rea

Re: Wrong clojure version depending on lein dependencies (was: ANN: Clojure 1.5)

Hi Wolodja, It's useful to note that you can use the currently preferred fixed version specifiers and still have your dependencies and the top-level project depend on multiple versions of a library (the common case is multiple versions of Clojure specified as dependencies). Also, you can specify

Re: Wrong clojure version depending on lein dependencies (was: ANN: Clojure 1.5)

Hi Chas, Am Montag, 4. März 2013 14:33:29 UTC+1 schrieb Chas Emerick: > > There are a lot of reasons for this, but #1 for me is that few people > understand the implications of version ranges, either downstream of their > published libraries or when they are consuming a library and place a range

Re: Wrong clojure version depending on lein dependencies

"Meikel Brandmeyer (kotarak)" writes: > Hi, > > Am Montag, 4. März 2013 13:00:31 UTC+1 schrieb Wolodja Wentland: >> >> It is up to a community to fix things that are broken in their toolset and >> "Do not use version ranges" is IMHO the wrong answer. >> > Huge +1. Fixing version ranges seems l

Re: Wrong clojure version depending on lein dependencies (was: ANN: Clojure 1.5)

On Mar 4, 2013, at 7:36 AM, Meikel Brandmeyer (kotarak) wrote: > Hi, > > Am Montag, 4. März 2013 13:00:31 UTC+1 schrieb Wolodja Wentland: > > It is up to a community to fix things that are broken in their toolset and > "Do > not use version ranges" is IMHO the wrong answer. > > > Huge +1. >

Re: Wrong clojure version depending on lein dependencies (was: ANN: Clojure 1.5)

Hi, Am Montag, 4. März 2013 13:00:31 UTC+1 schrieb Wolodja Wentland: > > > It is up to a community to fix things that are broken in their toolset and > "Do > not use version ranges" is IMHO the wrong answer. > > Huge +1. I was about to blog in favour of version ranges. As I'm a toolmaker mysel

Re: Wrong clojure version depending on lein dependencies (was: ANN: Clojure 1.5)

On Sat, Mar 02, 2013 at 17:42 -0600, Nelson Morris wrote: > > Or is this a bug in leiningen's dependency resolution? > Unfortunately it's behaviour defined by maven. In order to be compatible > lein has to do the same thing. > I've written up a few things about version ranges at > http://nelson

Re: Wrong clojure version depending on lein dependencies

Excellent - thanks for letting me know - Frank. On Mar 3, 2013, at 11:37 PM, Tassilo Horn wrote: > Frank Siebenlist writes: > > Hi Frank, > >> clj-ns-browser 1.3.1 is released and addresses this issue by upgrading >> the project's dependencies to seesaw 1.4.3. > > With 1.3.1 I could remove

Re: Wrong clojure version depending on lein dependencies

Frank Siebenlist writes: Hi Frank, > clj-ns-browser 1.3.1 is released and addresses this issue by upgrading > the project's dependencies to seesaw 1.4.3. With 1.3.1 I could remove all the :excusions again and it still picked the right clojure version (1.5.0). Thanks, Tassilo -- -- You recei

Re: Wrong clojure version depending on lein dependencies (was: ANN: Clojure 1.5)

clj-ns-browser 1.3.1 is released and addresses this issue by upgrading the project's dependencies to seesaw 1.4.3. For docs and code, please see "https://github.com/franks42/clj-ns-browser";. Enjoy, Frank. On Mar 2, 2013, at 10:57 PM, Dave Ray wrote: >>> As i'm responsible for the clj-ns-br

Re: Wrong clojure version depending on lein dependencies (was: ANN: Clojure 1.5)

>> As i'm responsible for the clj-ns-browser release... >> And although the dependency issue seems another 2 levels down, can i specify >> anything differently in my project file to prevent this? > > You could add the a similar exclusion for org.clojure/clojure in the > seesaw dependency declarati

Re: Wrong clojure version depending on lein dependencies (was: ANN: Clojure 1.5)

On Sat, Mar 2, 2013 at 4:17 PM, Frank Siebenlist wrote: >> ... >> The chain causing problems for you is: >> >> [clj-ns-browser "1.3.0"] -> [seesaw "1.4.2"] -> [j18n "1.0.1"] -> >> [org.clojure/clojure "[1.2,1.5)"] >> >> The last one there allows clojure below 1.5, which includes -RC17. As >> soon

Re: Wrong clojure version depending on lein dependencies (was: ANN: Clojure 1.5)

I'll push a new release of seesaw this weekend to isolate the issue. It seems like a clj-ns-browser release with the new seesaw version would then be appropriate. Nelson pointed this issue out to me a while ago, but 1.5 seemed so far off at the time. Sorry about the pain. Dave On Sat, Mar 2, 201

Re: Wrong clojure version depending on lein dependencies (was: ANN: Clojure 1.5)

> ... > The chain causing problems for you is: > > [clj-ns-browser "1.3.0"] -> [seesaw "1.4.2"] -> [j18n "1.0.1"] -> > [org.clojure/clojure "[1.2,1.5)"] > > The last one there allows clojure below 1.5, which includes -RC17. As > soon as you bump to to 1.5 it ignores the "soft" version in your >

Re: Wrong clojure version depending on lein dependencies

Nelson Morris writes: Hi Nelson, > The chain causing problems for you is: > > [clj-ns-browser "1.3.0"] -> [seesaw "1.4.2"] -> [j18n "1.0.1"] -> > [org.clojure/clojure "[1.2,1.5)"] > > The last one there allows clojure below 1.5, which includes -RC17. As > soon as you bump to to 1.5 it ignores t

Re: Wrong clojure version depending on lein dependencies (was: ANN: Clojure 1.5)

On Fri, Mar 1, 2013 at 1:24 PM, Tassilo Horn wrote: > Michael Klishin writes: > >> 2013/3/1 Tassilo Horn >> >>> So to summarize: >>> >>> clj 1.5.0-RC17 + ordered 1.3.2 => clj 1.5.0-RC17 is used >>> clj 1.5.0 + ordered 1.3.2 => clj 1.4.0 is used >>> clj 1.5.0 no ordered 1.3.2 => cl

Wrong clojure version depending on lein dependencies (was: ANN: Clojure 1.5)

Michael Klishin writes: > 2013/3/1 Tassilo Horn > >> So to summarize: >> >> clj 1.5.0-RC17 + ordered 1.3.2 => clj 1.5.0-RC17 is used >> clj 1.5.0 + ordered 1.3.2 => clj 1.4.0 is used >> clj 1.5.0 no ordered 1.3.2 => clj 1.3.0 is used >> >> Can anymone make sense of that? > > This