FWIW, I reported https://issues.apache.org/jira/browse/INFRA-12941.
Regards Julian On Fri, Nov 18, 2016 at 6:20 PM, Konrad Windszus <[email protected]> wrote: > This issue definitely is an infrastructure issue with Maven Central. I opened > https://issues.sonatype.org/browse/MVNCENTRAL-1369 about the wrong > certificate currently in place for https://repo.maven.apache.org. > Konrad >> >> Waiting for Jenkins to finish collecting data >> [ERROR] Failed to execute goal >> org.apache.maven.plugins:maven-dependency-plugin:2.8:copy >> (prepare-launchpad) on project org.apache.sling.ide.eclipse-test: Unable to >> resolve artifact. Could not transfer artifact >> org.apache.sling:org.apache.sling.launchpad:war:7 from/to central >> (https://repo.maven.apache.org/maven2): hostname in certificate didn't >> match: <repo.maven.apache.org> != <repo1.maven.org> OR <repo1.maven.org> >> [ERROR] org.apache.sling:org.apache.sling.launchpad:war:7 >> [ERROR] >> [ERROR] from the specified remote repositories: >> [ERROR] Nexus (http://repository.apache.org/snapshots, releases=false, >> snapshots=true), >> [ERROR] central (https://repo.maven.apache.org/maven2, releases=true, >> snapshots=false) >> [ERROR] -> [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/MojoExecutionException >> [ERROR] >> [ERROR] After correcting the problems, you can resume the build with the >> command >> [ERROR] mvn <goals> -rf :org.apache.sling.ide.eclipse-test >> Xvfb stopping >> channel stopped >> Found 39 test results >> Found 11 test results >> Found 60 test results >
