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
Import correct resolver from librarymanagement #746
Import correct resolver from librarymanagement #746
Conversation
Ok, this doesn't work on 0.13, as sbt.librarymanagement.Resolver isn't in sbt-compat yet. I've added a PR for this: dwijnand/sbt-compat#8 |
I'm getting test failures that seem unrelated:
jquery 3.3.0 and 3.3.1 were released two days ago. Seems that the real world has changed. I'm going to fix the test, if that's ok. |
Closing and reopening to rerun CI. |
Ok, now I'm officially confused. When I change the test expectation, the test fails because it is expecting version 3.2.1, which is the old version of jquery. Can you help? |
@leonardehrenfried I'll have a look. I think the failing test might need to be put behind a condition like that one. The main tests just rely on what's in this repo, so shouldn't need to be updated like this. But the tests are also run via docker-based Nexus proxies, which download stuff… The |
@leonardehrenfried Rebase if you'd like (as the nexus proxy tests are disabled), CI should be fine then. |
Ok, rebased. |
@leonardehrenfried You want this to be merged, right? (I mean, it's not just for testing?) |
Yes, I'd like this to be merged. Even if it doesn't resolve my issue, it is
the correct import.
Am 31.01.2018 2:11 nachm. schrieb "Alexandre Archambault" <
notifications@github.com>:
… @leonardehrenfried <https://github.com/leonardehrenfried> You want this
to be merged, right? (I mean, it's not just for testing?)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#746 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAJPModhTWdQeCqpsLIVxuAvWdh6dYV7ks5tQGZxgaJpZM4Rk2Yx>
.
|
Ok, merging then! |
This might be a solution for #745 by importing the correct version of the
Resolver
type fromsbt.librarymanagement
rather thansbt
thereby sidestepping the issue described here: sbt/librarymanagement#190 (comment)