Repo is fine: http://repository.cloudera.com/artifactory/cloudera-repos/
This artifact has never been in the Cloudera repo actually. As I mentioned I am able to build successfully even if the repo is completely gone, as a result. The Spark build actually does not use the Cloudera repo, as Patrick says. It's there for convenience. Whatever is going on -- you could just remove the repo declaration for the moment. What I *do* see is that if you access it over https, it says the cert is expired: https://repository.cloudera.com/artifactory/cloudera-repos/ I will ask Andrew B about that since that's of course no good. That's consistent with "peer not authenticated" but still not clear why it only fails the build for you. What Maven version? One solution is to use a HTTP URL for the repo. I can suggest another solution to whatever this is, which is to put the Eclipse repo up in the parent pom, and ahead of the Cloudera repo. This causes it to be tried first, which is appropriate. Any +1 for either of those changes? -- Sean Owen | Director, Data Science | London On Fri, Mar 14, 2014 at 7:37 AM, Tom Graves <tgraves...@yahoo.com> wrote: > It appears the cloudera repo for the mqtt stuff is down again. > > Did someone ping them the last time? > > Can we pick this up from some other repo? > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-remote-resources-plugin:1.4:process > (default) on project spark-examples_2.10: Error resolving project artifact: > Could not transfer artifact org.eclipse.paho:mqtt-client:pom:0.4.0 from/to > cloudera-repo (https://repository.cloudera.com/artifactory/cloudera-repos): > peer not authenticated for project org.eclipse.paho:mqtt-client:jar:0.4.0 > > Tom
