Bump sbt version to 0.13.9 #666
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There are several issues that report compilation errors with a message like:
[error] impossible to get artifacts when data has not been loaded. IvyNode = com.fasterxml.jackson.core#jackson-databind;2.5.4
java.lang.IllegalStateException: impossible to get artifacts when data has not been loaded. IvyNode = com.fasterxml.jackson.core#jackson-databind;2.5.4
Examples:
- linkedin#201
- linkedin#339
- linkedin#367
- linkedin#419
- linkedin#658
It looks like this message stems from a bug in Ivy which has since been fixed
(sbt/sbt#1598). I'm guessing the fix in Ivy is
included in sbt v0.13.9, because uprading sbt fixed the issue for me, and seems
to have helped others, too (e.g.,
linkedin#201 (comment)).
ShubhamGupta29
approved these changes
Mar 24, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
There are several issues that report compilation errors with a message like:
Examples:
It looks like this message stems from a bug in Ivy which has since been fixed
(sbt/sbt#1598). I'm guessing the fix in Ivy is
included in sbt v0.13.9, because upgrading sbt fixed the issue for me, and seems
to have helped others, too (e.g., #201 (comment)).