sbt, the interactive build tool
Go to file
eugene yokota ac571371c6 Fixes sbt/sbt#2264. Use explicit artifacts if any, fallback to hardcoded
Even though it's not really used, updateClassifiers constructs
dependency graph based on the result from update.
The direct cause of sbt/sbt#2264 came from the fact that the `allModules`
returned from ConfigurationReport did not include dependency
configurations. For example it returned "compile" instead of
"compile->runtime". I've identified that in #2264 and was fixed by
@Duhemm in sbt/sbt@f49fb33.

Martin identified that the fix still does not address the fact that
updateClassifier hardcodes the classifiers to be tried. This commit
adds the fallback behavior so for Ivy-published modules it will use the
explicit list of artifacts, and for others it will fallback to the
hardcoded list of classifiers.
2015-12-03 17:23:32 +01:00
librarymanagement Fixes sbt/sbt#2264. Use explicit artifacts if any, fallback to hardcoded 2015-12-03 17:23:32 +01:00
project Update to latest sbt-houserules, formatting 2015-09-16 14:57:00 +02:00
.travis.yml Merge #1 2015-09-02 03:03:20 -04:00
README.md Add build.sbt 2015-08-19 03:56:08 -04:00
build.sbt Remove more redundant settings 2015-09-18 09:05:43 +01: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