Eugene Yokota 54564ba7ce 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-02-10 04:00:04 -05:00
..
buildlevelkey.md	Touch up exisiting 0.13.14 notes	2017-02-06 10:24:10 +00:00
dotty_bridge.md	Automatically choose proper compiler bridge for dotty	2017-01-11 16:06:45 +01:00
fix-triggeredBy-storeAs-etc-using-colon-equals.md	Add notes for .triggeredBy/.storeAs/etc fix	2017-02-06 10:24:15 +00:00
ivyfix.md	Bump up Ivy	2016-11-11 14:42:48 -05:00
junit_xml_imp.md	Touch up exisiting 0.13.14 notes	2017-02-06 10:24:10 +00:00
mavenversionrange.md	Maven version range improvement	2017-02-10 04:00:04 -05:00
mediator_fix.md	Apply binary version conflict check to Compile related configs	2016-11-11 15:44:05 -05:00
preliminary-compatibility-with-jdk9.md	Add notes for preliminary compatbility with jdk 9	2017-02-06 10:24:12 +00:00