[
https://issues.jboss.org/browse/SHRINKWRAP-449?page=com.atlassian.jira.pl...
]
Michal Matloka commented on SHRINKWRAP-449:
-------------------------------------------
From ant manual but describes tar behaviour.
http://ant.apache.org/manual/Tasks/tar.html
{noformat}
Early versions of tar did not support path lengths greater than 100 characters. Modern
versions of tar do so, but in incompatible ways. The behaviour of the tar task when it
encounters such paths is controlled by the longfile attribute. If the longfile attribute
is set to fail, any long paths will cause the tar task to fail. If the longfile attribute
is set to truncate, any long paths will be truncated to the 100 character maximum length
prior to adding to the archive. If the value of the longfile attribute is set to omit then
files containing long paths will be omitted from the archive. Either option ensures that
the archive can be untarred by any compliant version of tar.
{noformat}
TarGzExporter wrong packing of paths with more than 100 characters
------------------------------------------------------------------
Key: SHRINKWRAP-449
URL:
https://issues.jboss.org/browse/SHRINKWRAP-449
Project: ShrinkWrap
Issue Type: Bug
Components: impl-base
Reporter: Matej Lazar
Prefixes of long paths (> 100 chars) are ignored when unpacking archives with tar on
linux.
Packing "moreThan100/long/path/to/file.class" with TarGzExporter, is unpacked
by linux tar as "long/path/to/file.class".
Where "long/path/to/file.class" is just bellow 100 chars.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira