Yes, I'm using Maven 3.2.1. Actually, scratch that, it fails for me too once it gets down into the MQTT module, with a clearer error:
sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: timestamp check failed for project org.eclipse.paho:mqtt-client:jar:0.4.0: NotAfter: Fri Mar 14 05:23:38 PDT 2014 -> [Help 1] Yep, expired 3 hours ago. HTTP is a fine workaround for now (or just remove the declaration entirely). I suppose it's slightly better to use HTTPS in the long-run, to ensure the authenticity of the source. Of course the repo's cert is going to be fixed shortly. So I suggest HTTPS should be used for all repos, and it's not right now in the build. (Although, by default, Maven uses an HTTP URL for its own repo, hmm.) But I still think it's more sensible to move repo declarations up into the parent, where their order can be controlled as desired. Child pom repos come after parent repos and that, while it rarely makes any difference, isn't actually desirable. I'll prep a PR but wait for someone else to second a change like that. -- Sean Owen | Director, Data Science | London On Fri, Mar 14, 2014 at 7:57 AM, Tom Graves <tgraves...@yahoo.com> wrote: > Thanks Sean, > > I assume you are building with maven and not sbt? It completely fails > for me. maven version is 3.1.0. I'm also building for yarn but I don't > think that matters (mvn -Dyarn.version=0.23.10 -Dhadoop.version=0.23.10 > -Pyarn-alpha package -DskipTests). > > I changed the pom to use http rather then https and it works now for me. > > Tom > > > > On Friday, March 14, 2014 9:53 AM, Sean Owen <so...@cloudera.com> wrote: > > 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 >
