The default manager configuration in providers.xml registers the Tar and Bzip2FileProvider conditionally based on commons compress classes. For GzipFileProvider it uses unconditionally the java.util.zip package.
<provider class-name="org.apache.commons.vfs2.provider.tar.TarFileProvider"> <scheme name="tar" /> <if-available class-name="org.apache.commons.compress.archivers.tar.TarArchiveOutputStream" /> </provider> <provider class-name="org.apache.commons.vfs2.provider.bzip2.Bzip2FileProvider"> <scheme name="bz2" /> <if-available class-name="org.apache.commons.compress.compressors.bzip2.BZip2CompressorInputStream" /> </provider> <provider class-name="org.apache.commons.vfs2.provider.gzip.GzipFileProvider"> <scheme name="gz" /> </provider> So I agree, the download page should be changed accordingly. Only the two providers have this dependency. Gruss Bernd Am Sat, 03 May 2014 12:36:27 +0100 schrieb Schalk Cronjé <ysb...@gmail.com>: > With 2.0 tar is supported out of the box, with 2.1 it is not. It > depends on commons-compress which is listed as an optional dependency. > > Is this intentional? If so the documentation > (http://commons.apache.org/proper/commons-vfs/download.html) needs to > be updated prior to release. > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org