sbt/librarymanagement
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
..
src Fixes sbt/sbt#2264. Use explicit artifacts if any, fallback to hardcoded 2015-12-03 17:23:32 +01:00
NOTICE Add build.sbt 2015-08-19 03:56:08 -04:00