-
Notifications
You must be signed in to change notification settings - Fork 32
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
Maven installation fails - Dependencies issues #18
Comments
@rnewson is it possible we return it to http://maven.cloudant.com? It's pointing to https://maven.cloudant.com causing the build to fail. |
um, I did a while ago, update? |
Still failing "stdout_lines": [ Still cant reach http://maven.cloudant.com/repo/ |
Hi, I got a bit confused here. I've put the url back to https://maven.cloudant.org/repo. |
Hmm strange, still not working "stdout_lines": [ |
can you visit |
I can not sure why its failing. Below is the full error "changed": true, |
Are you sure you aren't having other networking/firewall issues preventing your outbound requests? Try the url in my last comment with curl or wget on the same machine. |
I doubt, I've installed other packages, this is the only one bringing issues. I'm puzzled. |
have you tried the curl command yet? |
Yeah I can curl sudo curl -k https://maven.cloudant.com/repo/ <title>Index of /repo/</title>Index of /repo/../ com/ 30-Jan-2017 21:08 - jsr166y/ 30-Jan-2017 21:08 - org/ 30-Jan-2017 21:08 - |
hm, ok (no idea why you sudo'ed that, that's a bad habit you should break). have you configured maven to use a proxy maybe? (~/.m2/settings.xml iirc). |
Cool will not use sudo :-) I haven't configured any proxies. Find below my settings.xml `
|
Can we try switching it http://maven.cloudant.com/repo/ instead of https? |
nope, because we've closed port 80 across our whole infrastructure and I'm not going to reverse that here. my maven install can contact https://maven.cloudant.com/repo and pull down all the artifacts. I don't understand why yours can't. :( |
Hmm did a fresh install of the OS and I'm still encountering the same issue. Strange....it uses the same repo for Ubuntu 16.04 Xenial? |
yup, same repo, it's the same jar for every OS. I'm not really sure what to suggest you try next. |
Maven installation fails with dependency issues. Below is the error.
"stdout_lines": [
"[INFO] Scanning for projects...",
"[INFO] ",
"[INFO] ------------------------------------------------------------------------",
"[INFO] Building clouseau 2.10.0-SNAPSHOT",
"[INFO] ------------------------------------------------------------------------",
"Downloading: http://maven.cloudant.com/repo/com/boundary/scalang-scala_2.9.1/0.28-cloudant2/scalang-scala_2.9.1-0.28-cloudant2.pom",
"",
"[INFO] ------------------------------------------------------------------------",
"[INFO] BUILD FAILURE",
"[INFO] ------------------------------------------------------------------------",
"[INFO] Total time: 1.626 s",
"[INFO] Finished at: 2018-03-19T15:02:08+00:00",
"[INFO] Final Memory: 24M/962M",
"[INFO] ------------------------------------------------------------------------",
"[ERROR] Failed to execute goal on project clouseau: Could not resolve dependencies for project com.cloudant:clouseau:jar:2.10.0-SNAPSHOT: Failed to collect dependencies at com.boundary:scalang-scala_2.9.1:jar:0.28-cloudant2: Failed to read artifact descriptor for com.boundary:scalang-scala_2.9.1:jar:0.28-cloudant2: Could not transfer artifact com.boundary:scalang-scala_2.9.1:pom:0.28-cloudant2 from/to CloudantPublicRepo (http://maven.cloudant.com/repo/): Connect to maven.cloudant.com:80 [maven.cloudant.com/50.97.193.79] failed: Connection refused -> [Help 1]",
"[ERROR] ",
"[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.",
"[ERROR] Re-run Maven using the -X switch to enable full debug logging.",
"[ERROR] ",
"[ERROR] For more information about the errors and possible solutions, please read the following articles:",
"[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException"
]
}
The text was updated successfully, but these errors were encountered: