maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ben Douglas (JIRA)" <>
Subject [jira] (WAGON-381) Both Maven 2 and 3 fail to retrieve a <dependency> that is larger than Integer.MAX_VALUE
Date Wed, 16 Jan 2013 15:42:13 GMT


Ben Douglas commented on WAGON-381:

I just attempted the 3.1 snapshot (build 320) and my download stalled again and gave me a
bad md5 warning:

bdouglas@gambit templates$ /opt/apache-maven-3.1-SNAPSHOT/bin/mvn --version
Apache Maven 3.1-SNAPSHOT (rNON-CANONICAL_2012-12-01_03-31_jenkins; 2012-11-30 22:31:54-0500)
Maven home: /opt/apache-maven-3.1-SNAPSHOT
Java version: 1.6.0_33, vendor: Sun Microsystems Inc.
Java home: /opt/jdk1.6.0_33/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.6.11-1.fc17.x86_64", arch: "amd64", family: "unix"
bdouglas@gambit templates$

The checksum failing is when the artifact is only the Integer.MAX_VALUE size

[INFO] Configured Artifact: org.centos:CentOS-6.3-x86_64-bin-DVD1:1.0:iso
[DEBUG] Using connector WagonRepositoryConnector with priority 0 for
[WARNING] Checksum validation failed, expected eaa52f3d1ccf2df3b03e064fb0fa6168be28a4d4 but
is 249cf446611db34ad8006bbdb99397c2a4bc201a for

> Both Maven 2 and 3 fail to retrieve a <dependency> that is larger than Integer.MAX_VALUE
> ----------------------------------------------------------------------------------------
>                 Key: WAGON-381
>                 URL:
>             Project: Maven Wagon
>          Issue Type: Bug
>          Components: wagon-http
>    Affects Versions: 2.2
>            Reporter: Evgeny Goldin
>            Assignee: Olivier Lamy
>             Fix For: 2.3
>         Attachments: 1.png, 2.png
> We have a *{{*.tar}}* file stored in corporate Maven repository, its size is *{{2.5Gb}}*.
Trying to bring it with Maven (both 2 and 3) causes file of *{{2147483647}}* size to be downloaded
to local maven repo, which is exactly 2<sup>31</sup>-1.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message