This is a good point. Should we have Buildr depend on lock_jar? > Begin forwarded message: > > From: "Trejkaz (JIRA)" <[email protected]> > Subject: [jira] [Commented] (BUILDR-274) Support dependency version ranges > for transitive dependencies > Date: November 21, 2016 at 7:19:58 PM PST > To: [email protected] > Reply-To: [email protected] > > > [ > https://issues.apache.org/jira/browse/BUILDR-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15685541#comment-15685541 > ] > > Trejkaz commented on BUILDR-274: > -------------------------------- > > Arguably I shouldn't have to install some completely different dependency > resolver just to make a build tool resolve dependencies correctly, but maybe > that's just me. > > >> 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 > (v6.3.4#6332)
