sbt, the interactive build tool
Go to file
Eugene Yokota bb258f42a6 Maven version range improvement
Previously, when the dependency resolver (Ivy) encountered a Maven version range such as `[1.3.0,)`
it would go out to the Internet to find the latest version.
This would result to a surprising behavior where the eventual version keeps changing over time
*even when there's a version of the library that satisfies the range condition*.

This changes to some Maven version ranges would be replaced with its lower bound
so that when a satisfactory version is found in the dependency graph it will be used.
You can disable this behavior using the JVM flag `-Dsbt.modversionrange=false`.

Fixes #2954
Ref #2291 / #2953
2017-04-04 16:22:28 -04:00
librarymanagement Maven version range improvement 2017-04-04 16:22:28 -04:00
project Util 1.0.0-M20 2017-03-22 13:59:51 -04:00
.gitignore Maven version range improvement 2017-04-04 16:22:28 -04:00
.java-version Cross publish to Scala 2.12 2017-01-07 00:49:45 -05:00
.travis.yml Cross publish to Scala 2.12 2017-01-07 00:49:45 -05:00
README.md Add build.sbt 2015-08-19 03:56:08 -04:00
build.sbt Bump util 2017-01-13 22:48:32 -05:00
sbt-allsources.sh sbt-contraband 0.3.0-M4 2017-03-17 23:03:37 -04:00

README.md

librarymanagement module for sbt

git clone --no-hardlinks --branch 0.13 sbt sbt-modules/librarymanagement
cd sbt-modules/librarymanagement
git filter-branch --index-filter 'git rm --cached -qr -- . && git reset -q $GIT_COMMIT -- ivy util/cross' --prune-empty
git reset --hard
git gc --aggressive
git prune
git cb 1.0