sbt/notes/0.13.10/fix-updateclassifiers-confi...


  [@eed3si9n]: https://github.com/eed3si9n
  [@Duhemm]: https://github.com/Duhemm
  [2264]: https://github.com/sbt/sbt/issues/2264

### Fixes with compatibility implications

### Improvements

### Bug fixes

- Fixes `updateClassifiers` on Ivy modules without `default` configuration.
  [#2264][2264] by [@eed3si9n][@eed3si9n]/[@Duhemm][@Duhemm]
Fixes #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 #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 f49fb33e6d6bc82d86969fbc740341c45a742567. 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-02 22:41:02 +01:00
			`[@eed3si9n]: https://github.com/eed3si9n`
			`[@Duhemm]: https://github.com/Duhemm`
			`[2264]: https://github.com/sbt/sbt/issues/2264`

			`### Fixes with compatibility implications`

			`### Improvements`

			`### Bug fixes`

			- Fixes `updateClassifiers` on Ivy modules without `default` configuration.
			`[#2264][2264] by [@eed3si9n][@eed3si9n]/[@Duhemm][@Duhemm]`