Murtaza Husain | 19 Jun 2012 02:20

Wildcards in Leiningen Dependencies Versions

Hi,

Does leiningen support wildcards in dependencies version numbers ? I would usually like to use the latest version for some library, and it would be nice if I can indicate it by using a wildcard, so tat I dont need to keep checking if a new version has been released.

Thanks,
Murtaza

--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure <at> googlegroups.com
Note that posts from new members are moderated - please be patient with your first post.
To unsubscribe from this group, send email to
clojure+unsubscribe <at> googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
Phil Hagelberg | 19 Jun 2012 02:32
Gravatar

Re: Wildcards in Leiningen Dependencies Versions

On Mon, Jun 18, 2012 at 5:20 PM, Murtaza Husain
<murtaza.husain <at> sevenolives.com> wrote:
> Does leiningen support wildcards in dependencies version numbers ? I would
> usually like to use the latest version for some library, and it would be
> nice if I can indicate it by using a wildcard, so tat I dont need to keep
> checking if a new version has been released.

You can do this, but it's not a good idea:
https://github.com/technomancy/leiningen/wiki/Repeatability

-Phil

--

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure <at> googlegroups.com
Note that posts from new members are moderated - please be patient with your first post.
To unsubscribe from this group, send email to
clojure+unsubscribe <at> googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en

Jason Lewis | 19 Jun 2012 06:35
Picon
Gravatar

Re: Wildcards in Leiningen Dependencies Versions

One thing I would like to see is something like the tiddle-wakka in Ruby Gemfiles,  ie,

gem 'foo',  '~> 1.2.3'

would match 1.2.x where x > 3, and so on for the most precise specified version number (major, minor, patch)

It's super effective.

On Jun 18, 2012 8:32 PM, "Phil Hagelberg" <phil <at> hagelb.org> wrote:
On Mon, Jun 18, 2012 at 5:20 PM, Murtaza Husain
<murtaza.husain <at> sevenolives.com> wrote:
> Does leiningen support wildcards in dependencies version numbers ? I would
> usually like to use the latest version for some library, and it would be
> nice if I can indicate it by using a wildcard, so tat I dont need to keep
> checking if a new version has been released.

You can do this, but it's not a good idea:
https://github.com/technomancy/leiningen/wiki/Repeatability

-Phil

--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure <at> googlegroups.com
Note that posts from new members are moderated - please be patient with your first post.
To unsubscribe from this group, send email to
clojure+unsubscribe <at> googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en

--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure <at> googlegroups.com
Note that posts from new members are moderated - please be patient with your first post.
To unsubscribe from this group, send email to
clojure+unsubscribe <at> googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
Tassilo Horn | 19 Jun 2012 08:22
Picon
Gravatar

Re: Wildcards in Leiningen Dependencies Versions

Phil Hagelberg <phil <at> hagelb.org> writes:

>> Does leiningen support wildcards in dependencies version numbers ? I
>> would usually like to use the latest version for some library, and it
>> would be nice if I can indicate it by using a wildcard, so tat I dont
>> need to keep checking if a new version has been released.
>
> You can do this, but it's not a good idea:
> https://github.com/technomancy/leiningen/wiki/Repeatability

I did use that, and as Phil points out ran into maven dependency issues.
My motivation was mainly that it's convenient when you get dependency
updates "for free", and I am pretty optimistic that my stuff usually
won't break if foobar-0.1.0 is updated to foobar-0.2.0.

Because of the dependency issues I stopped using version ranges, and in
the meantime I discovered the leiningen outdated plugin at

  https://github.com/ato/lein-outdated

Using that, running "lein outdated" tells you what dependencies have
received updates (on maven central, clojars, whatever you use), and you
can easily adjust versions and check if your project works with the new
versions, too.  That's about as convenient as version ranges, and it has
the added benefit of you knowing exactly what you've updated in case an
update really breaks something.

Bye,
Tassilo

--

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure <at> googlegroups.com
Note that posts from new members are moderated - please be patient with your first post.
To unsubscribe from this group, send email to
clojure+unsubscribe <at> googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en

Murtaza Husain | 20 Jun 2012 14:50

Re: Wildcards in Leiningen Dependencies Versions


Phil, Tasillo thanks for the reply. The plugin is very helpful.


On Tuesday, June 19, 2012 11:52:41 AM UTC+5:30, Tassilo Horn wrote:
Phil Hagelberg <phil <at> hagelb.org> writes:

>> Does leiningen support wildcards in dependencies version numbers ? I
>> would usually like to use the latest version for some library, and it
>> would be nice if I can indicate it by using a wildcard, so tat I dont
>> need to keep checking if a new version has been released.
>
> You can do this, but it's not a good idea:
> https://github.com/technomancy/leiningen/wiki/Repeatability

I did use that, and as Phil points out ran into maven dependency issues.
My motivation was mainly that it's convenient when you get dependency
updates "for free", and I am pretty optimistic that my stuff usually
won't break if foobar-0.1.0 is updated to foobar-0.2.0.

Because of the dependency issues I stopped using version ranges, and in
the meantime I discovered the leiningen outdated plugin at

  https://github.com/ato/lein-outdated

Using that, running "lein outdated" tells you what dependencies have
received updates (on maven central, clojars, whatever you use), and you
can easily adjust versions and check if your project works with the new
versions, too.  That's about as convenient as version ranges, and it has
the added benefit of you knowing exactly what you've updated in case an
update really breaks something.

Bye,
Tassilo

--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure <at> googlegroups.com
Note that posts from new members are moderated - please be patient with your first post.
To unsubscribe from this group, send email to
clojure+unsubscribe <at> googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en

Gmane