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 nmor...@nelsonmorris.net wrote:
On Sat, Mar 2, 2013 at 4:17 PM, Frank Siebenlist
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
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 myself,
I
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.
I was
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
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
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 reasons
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
On 4 March 2013 15:01, Meikel Brandmeyer (kotarak) m...@kotka.de 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
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.
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 a
On Mon, Mar 4, 2013 at 2:01 PM, Meikel Brandmeyer (kotarak)
m...@kotka.dewrote:
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
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
published
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.
http://docs.codehaus.org/display/MAVEN/
Dependency+Mediation+and+Conflict+Resolution#
DependencyMediationandConflictResolution-DependencyVersionRanges
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 fail
On Mon, Mar 4, 2013 at 2:55 PM, Wolodja Wentland babi...@gmail.com 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.
http://docs.codehaus.org/display/MAVEN/
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
of
On 4 March 2013 15:30, Wolodja Wentland babi...@gmail.com 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
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 dave...@gmail.com wrote:
As i'm responsible for
...
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
:dependencies, and
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,
On Sat, Mar 2, 2013 at 4:17 PM, Frank Siebenlist
frank.siebenl...@gmail.com 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
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 declaration, but
We are pleased to announce the release of Clojure 1.5.
Getting Clojure:
Web: http://clojure.org/downloads
Lein/Maven: :dependencies [[org.clojure/clojure 1.5.0]]
Note that it will take a few hours for the links above to become live,
as the completed build moves into Maven
Stuart Halloway stuart.hallo...@gmail.com writes:
Hi Stu,
We are pleased to announce the release of Clojure 1.5.
Great, except that if I change my project's dependency from 1.5.0-RC17
to 1.5.0, I get this error when trying to lein test. With RC17, it
works just fine.
--8---cut
Great news, congratulations on your release!
--
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your
first post.
To
Congrats and thanks to all those who contributed!
On Friday, March 1, 2013 7:56:58 AM UTC-8, stuart@gmail.com wrote:
We are pleased to announce the release of Clojure 1.5.
Getting Clojure:
Web: http://clojure.org/downloads
Lein/Maven: :dependencies
works for me... do you have some sort of version conflict perhaps?
user= (clojure-version)
1.5.0
user= (require '[clojure.core.reducers :as r])
nil
user= (r/fold + (range 1000))
499500
On Fri, Mar 1, 2013 at 4:46 PM, Tassilo Horn t...@gnu.org wrote:
Stuart Halloway stuart.hallo...@gmail.com
David Powell djpow...@djpowell.net writes:
Hi David,
works for me... do you have some sort of version conflict perhaps?
Indeed, you are right. With dependency [org.clojure/clojure 1.5.0],
my project's actually started with clojure 1.4.0. With
[org.clojure/clojure 1.5.0-RC17], it's started
Hi Tassilo, are you using java v1.6? because according to the changelog,
reducers need an extra lib to work on java 1.6, while 1.7 should be fine
as-is.
On Friday, March 1, 2013 5:46:50 PM UTC+1, Tassilo Horn wrote:
Stuart Halloway stuart@gmail.com javascript: writes:
Hi Stu,
We
Joey Ezechiëls jeanpaul...@gmail.com writes:
Hi Joey,
Hi Tassilo, are you using java v1.6? because according to the
changelog, reducers need an extra lib to work on java 1.6, while 1.7
should be fine as-is.
No, I use 1.7. The problem is that actually clojure 1.4.0 gets started
although my
Are you using any special libs? I just tried to reproduce your problem by
upgrading a relatively simple project to clojure 1.5 and got no problems.
Best regards,
Joey Ezechiëls
On Fri, Mar 1, 2013 at 7:45 PM, Tassilo Horn t...@gnu.org wrote:
Joey Ezechiëls jeanpaul...@gmail.com writes:
Hi
2013/3/1 Tassilo Horn t...@gnu.org
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 reminds me of
Michael Klishin michael.s.klis...@gmail.com writes:
2013/3/1 Tassilo Horn t...@gnu.org
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
Cosmin Stejerean cos...@offbytwo.com writes:
core.logic might not have any dependencies in its pom, but the parent
pom (pom.contrib) does depend on clojure 1.3.0 by default.
Aha, there are parent poms. I didn't know that. Are there also aunt
and uncle poms? (I love maven so much!) ;-)
On Mar 1, 2013, at 07:56, Stuart Halloway wrote:
The number of Clojure contributors continues to grow. Thanks to all
the people whose code is included in this release:
Aaron Bedra
...
Thanks to all involved!
I think that it would be appropriate (and possibly spur participation)
to give
On Fri, Mar 1, 2013 at 1:24 PM, Tassilo Horn t...@gnu.org wrote:
Michael Klishin michael.s.klis...@gmail.com writes:
2013/3/1 Tassilo Horn t...@gnu.org
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
Congratulations for every one involved in making clojure the most fun to
work language there is.
On Friday, 1 March 2013 12:56:58 UTC-3, stuart@gmail.com wrote:
We are pleased to announce the release of Clojure 1.5.
Getting Clojure:
Web: http://clojure.org/downloads
Congratulations on the new release. Thanks for all your hard work.
On Fri, Mar 1, 2013 at 5:08 PM, Jean Baro jfb...@gmail.com wrote:
Congratulations for every one involved in making clojure the most fun to
work language there is.
On Friday, 1 March 2013 12:56:58 UTC-3, stuart@gmail.com
39 matches
Mail list logo
