Handle source, docs artifacts correctly for Ivy #25
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Following up on #10, this contains the changes from sbt/sbt#1016 and sbt/sbt#1140.
A corresponding PR to sbt 1.0.x will follow and I will reference it here.
Please bear in mind that these changes were already accepted and merged into 0.14, but then subsequently forgotten when the 1.0 branch of
librarymanagement
was cut from sbt/sbt's0.13
branch. We've been using these changes internally at GSA Capital for almost two years now, and they are crucial to being able to resolve source and doc artifacts from an Ivy repository. They are also compatible with the way maven source/doc artifacts are currently being resolved.Therefore, we're very keen to get these merged as soon as possible.