Closed eklavya closed 6 years ago
This will be labeled as a bug and fixed shortly. Once the fix is applied the custom resolver should no longer be needed. I'll update this ticket once its fixed.
@eklavya Ok the fix for this is in master. In release v 1.6 coming out shortly you will no longer need to explicitly specify a repo in sbt. You will be able to include it just as you would with any other dependency. Keep an eye out for the release. I closed the ticket.
@eklavya v1.6.0 has now been released to maven central resolving your problem
Thanks @freemo for the help.
With default resolvers when using SBT you get:
In sbt builds you need to add the sonatype snapshot resolver for the dependency to resolve.
like this: