-
Notifications
You must be signed in to change notification settings - Fork 25
Bug: Errors resolving com.github.scopt:scopt_2.12:3.7.0 dependencies when building on a clean machine. #92
Comments
Weird, I can build the transitive dependency chain org.raml:webapi-parser:0.5.0 > com.github.amlorg:amf-webapi_2.12:4.0.3 > com.github.scopt:scopt_2.12:3.7.0 without problems after adding both the mulesoft and jitpack maven repositories on a blank machine although I am not using gradle but maven / clojure tools.deps. Per Gradle/RepositoryHandler get the impression that you need to have unique names for each maven repository. Try adding a name to build.gradle for each additional repo, @ullgren. |
Yes adding webapi-parser as a dependency in my own project works as expected. This error only seems to occur when building the examples project within this repository, without doing any modifications to the code. |
I am having a similar issue when attempting to build the example project as well as importing the decencies into a separate project. My build output says this: Even with commenting out the specific When you enter I believe from the dependency |
Library version used
master and v0.5.0
Language library used with
Java
Describe the bug
Errors resolving dependencies when building on a clean machine.
Building the Java examples end in a 401 error when resolving the transient dependency com.github.scopt:scopt_2.12:3.7.0
Code that causes a bug
The
examples/java
code in the repo.Same problem with master and tag v0.5.0
Input
N/A
Actual behaviour/output/error
See build log below.
This is on a clean machine that has not previously build the project
Expected behaviour/output
The build should complete successfully.
Additional context
Console output:
The text was updated successfully, but these errors were encountered: