Trejkaz commented on BUILDR-274:

That seems like an odd thing to say.

If Buildr is about defining your dependencies, version ranges are obviously 
something you would want, because your true dependencies are _almost never_ a 
single specific version, and locking your dependencies to a specific version of 
something else just guarantees that people trying to use both your code and 
some other person's will get clashes at resolution-time.

> Support dependency version ranges for transitive dependencies
> -------------------------------------------------------------
>                 Key: BUILDR-274
>                 URL: https://issues.apache.org/jira/browse/BUILDR-274
>             Project: Buildr
>          Issue Type: New Feature
>          Components: Dependency management
>            Reporter: Martin Grotzke
>             Fix For: Wish List
> It seems that right now dependency version ranges as shown here [1] are not 
> supported.
> A version range is e.g. used by ehcache-web ([2]), so that when I use
>   transitive('net.sf.ehcache:ehcache-web:jar:1.6.0-beta2')
> buildr fails with this error:
>   Failed to download net.sf.ehcache:ehcache:pom:[1.6.0-beta4,], tried the 
> following repositories...
> It would be great to have support for version ranges, otherwise some libs 
> cannot be used with transitive().
> [1] 
> http://www.sonatype.com/books/maven-book/reference/pom-relationships-sect-version-ranges.html
> [2] 
> http://repo1.maven.org/maven2/net/sf/ehcache/ehcache-web/1.6.0-beta2/ehcache-web-1.6.0-beta2.pom

This message was sent by Atlassian JIRA

Reply via email to