This error clarifies what’s been happening with the oss-parent POM (and 
checksum) downloads: the Sonatype OSS repository doesn’t have them for version 
3 or 5, and is apparently sending 301 redirects.  The Solr test framework 
module includes this repository in its POM.

I’ve downloaded the version 5 .pom & .sha1 files to the local maven repository 
on the Lucene zone (did that yesterday for version 3), and hopefully that will 
at least temporarily allow the build to continue.

I plan on investigating ordering the central repository before the Sonatype OSS 
repository for the Solr test framework module.  I’ll also report the problem to 
Sonatype.

Steve

> On Feb 26, 2015, at 5:28 AM, Apache Jenkins Server 
> <[email protected]> wrote:
> 
> Build: https://builds.apache.org/job/Lucene-Solr-Maven-5.x/856/
> 
> No tests ran.
> 
> Build Log:
> [...truncated 37763 lines...]
> -validate-maven-dependencies:
[…]
> [artifact:dependencies] Downloading: 
> org/sonatype/oss/oss-parent/5/oss-parent-5.pom from repository 
> sonatype.releases at http://oss.sonatype.org/content/repositories/releases
> [artifact:dependencies] Transferring 0K from sonatype.releases
> [artifact:dependencies] [WARNING] *** CHECKSUM FAILED - Checksum failed on 
> download: local = '81ffbd1712afe8cdf138b570c0fc9934742c33c1'; remote = '<html>
> [artifact:dependencies] <head><title>301' - RETRYING
> [artifact:dependencies] Downloading: 
> org/sonatype/oss/oss-parent/5/oss-parent-5.pom from repository 
> sonatype.releases at http://oss.sonatype.org/content/repositories/releases
> [artifact:dependencies] Transferring 0K from sonatype.releases
> [artifact:dependencies] [WARNING] *** CHECKSUM FAILED - Checksum failed on 
> download: local = '81ffbd1712afe8cdf138b570c0fc9934742c33c1'; remote = '<html>
> [artifact:dependencies] <head><title>301' - IGNORING
> [artifact:dependencies] An error has occurred while processing the Maven 
> artifact tasks.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to