I had the same problem. Looks like this is just what the downloading process does. Check out:
http://maven.apache.org/wagon/wagon-providers/wagon-http/xref/org/apache/maven/wagon/providers/http/HttpWagon.html#378 If the "content-encoding" of the dependency is gzip, then the http client that does the downloading unzips it in transit. Wonderful. Anders Blehr wrote: > > List, > > I have a gzipped tarball type artifact (<packaging>tar.gz</packaging>) in > my > repository and a dependency to it (with <type>tar.gz</type>) in my POM. > All > I want is for the dependency to be resolved and the artifact to be copied > to > my local repository so that I can copy it out to where it really should > go. > However, the resolved artifact that ended up in my local repository was > 'not > in gzip format' according to gzip/tar. > > After lengthy investigations I have found out that Maven somehow (and for > some as yet unknown reason) *unpacks* the tarball before/during dependency > resolution. I.e., the resolved artifact in my local repository is no > longer > a .tar.gz, just a .tar (Maven doesn't touch the .tar.gz extension/type, > though). > > The same happens if I specify the packaging type as tgz or just gz. If I > use zip, though, it does not unpack. > > Does anyone know why this is, and whether this behaviour is by design or > not? Is it possible to turn off the unpacking!? > > Thanks in advance, > - Anders. > > Anders Blehr > Senior Solutions Architect > FAST > Torggata 2-4-6 > N-0181 Oslo, Norway > www.fastsearch.com > > > -- View this message in context: http://www.nabble.com/Artifact-with-type-tar.gz-%28or-tgz-or-gz%29-unpacked-during-dependency-resolution%3A-Why--tf4486660s177.html#a12907949 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
