[
https://issues.apache.org/jira/browse/COMPRESS-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig updated COMPRESS-182:
------------------------------------
Description:
This is a superset of the functionality that addressed COMPRESS-175
Jörg Schillig's star and GNU tar may use binary encoding for all numeric
fields, PAX/POSIX also provides them inside the extension headers.
The timestamp field may even contain negative numbers.
IMHO Commons Compress should:
* be able to parse numeric fields using binary encoding (positive and negative)
* fix the current binary parser (see discussion in COMPRESS-16) and add a
workaround for broken writers (see COMPRESS-181)
* be able to parse all standard fields of PAX headers, including the numeric
ones (I haven't checked, maybe it already does)
* have an option to write numbers too big/small in binary encoding much like
BIGFILE_STAR does for the file size in trunk
* have an option to write numbers too big/small in PAX headers much like
BIGFILE_POSIX does for the file size in trunk
* replace bigFileMode and the constants with a more generic property that
controls all numeric fields. We can remove the bigFileMode stuff as it has
been added after the 1.3 release.
was:
This is a superset of the functionality that addressed COMPRESS-175
Jörg Schillig's star and GNU tar may use binary encoding for all numeric
fields, PAX/POSIX also provides them inside the extension headers.
The timestamp field may even contain negative numbers.
IMHO Commons Compress should:
* be able to parse numeric fields using binary encoding (positive and negative)
* fix the current binary parser (see discussion in COMPRESS-16) and add a
workaround for broken writers (see COMPRESS-181
* be able to parse all standard fields of PAX headers, including the numeric
ones (I haven't checked, maybe it already does)
* have an option to write numbers too big/small in binary encoding much like
BIGFILE_STAR does for the file size in trunk
* have an option to write numbers too big/small in PAX headers much like
BIGFILE_POSIX does for the file size in trunk
* replace bigFileMode and the constants with a more generic property that
controls all numeric fields. We can remove the bigFileMode stuff as it has
been added after the 1.3 release.
> Support big or even negative numbers in all numeric TAR headers
> ---------------------------------------------------------------
>
> Key: COMPRESS-182
> URL: https://issues.apache.org/jira/browse/COMPRESS-182
> Project: Commons Compress
> Issue Type: Improvement
> Components: Archivers
> Affects Versions: 1.3
> Reporter: Stefan Bodewig
> Fix For: 1.4
>
>
> This is a superset of the functionality that addressed COMPRESS-175
> Jörg Schillig's star and GNU tar may use binary encoding for all numeric
> fields, PAX/POSIX also provides them inside the extension headers.
> The timestamp field may even contain negative numbers.
> IMHO Commons Compress should:
> * be able to parse numeric fields using binary encoding (positive and
> negative)
> * fix the current binary parser (see discussion in COMPRESS-16) and add a
> workaround for broken writers (see COMPRESS-181)
> * be able to parse all standard fields of PAX headers, including the numeric
> ones (I haven't checked, maybe it already does)
> * have an option to write numbers too big/small in binary encoding much like
> BIGFILE_STAR does for the file size in trunk
> * have an option to write numbers too big/small in PAX headers much like
> BIGFILE_POSIX does for the file size in trunk
> * replace bigFileMode and the constants with a more generic property that
> controls all numeric fields. We can remove the bigFileMode stuff as it has
> been added after the 1.3 release.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
