Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(Do not merge) Fixes sbt/sbt#2264. Use explicit artifacts if any, fallback to hardcoded #2300

Closed
wants to merge 2 commits into from

Conversation

Duhemm
Copy link
Contributor

@Duhemm Duhemm commented Dec 7, 2015

This is a port for #2297. This won't compile until we have a new release of sbt/librarymanagement that includes both sbt/librarymanagement#9 and sbt/librarymanagement#13.

Even though it's not really used, updateClassifiers constructs
dependency graph based on the result from update.
The direct cause of 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 sbt#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.
@typesafe-tools
Copy link

Can one of the admins verify this patch?

@dwijnand dwijnand modified the milestones: 1.0, 1.0.0 Jan 17, 2016
@eed3si9n
Copy link
Member

This change is in direct conflict with the change added in #2478.
Maybe we need to add a separate task for updateClassifiers and the task that grabs sources and docs.

@eed3si9n
Copy link
Member

eed3si9n commented May 2, 2016

I'm going to close this PR for now.

@eed3si9n eed3si9n closed this May 2, 2016
@eed3si9n eed3si9n modified the milestones: 1.0.0, 1.0 May 13, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants