You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2010/01/12 17:12:55 UTC
[jira] Moved: (WAGON-299) tgz artifacts ungzipped on download
[ http://jira.codehaus.org/browse/WAGON-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter moved MNG-3233 to WAGON-299:
-----------------------------------------
Fix Version/s: (was: 2.2.x)
1.0
Affects Version/s: (was: 2.0.7)
(was: 2.0.6)
(was: 2.0.5)
Key: WAGON-299 (was: MNG-3233)
Project: Maven Wagon (was: Maven 2 & 3)
> tgz artifacts ungzipped on download
> -----------------------------------
>
> Key: WAGON-299
> URL: http://jira.codehaus.org/browse/WAGON-299
> Project: Maven Wagon
> Issue Type: Bug
> Reporter: Steinar Bang
> Fix For: 1.0
>
>
> If a tgz artifact (in our case DLLs and shared libs for different platforms, that accompany a JNI wrapper Java library), is dowloaded from a maven repository on an HTTP server that sets the HTTP header "content-encoding: gzip" on the download, the downloaded file will be ungzipped before storing it in the local maven repository, still with the extension .tgz, and dependency:unpack will fail when attempting to unpack the library.
> This has been an upgrade blocker and have stuck us on version 2.0.4, which is getting increasingly hard, so from our POV it's at least priority "Major".
> We first encountered this problem on 2.0.5, and I unintentionally verified today that it's present in 2.0.7.
> I'm guessing it is in maven itself rather than in the maven-dependency-plugin, which is where we see it, because the same version of the maven-dependency-plugin works on 2.0.4, and fails on later mavens.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira