On 21/05/2010, Stefan Bodewig <[email protected]> wrote: > On 2010-05-21, Christian Grobmeier wrote: > > > COMPRESS-75 > > ZipArchiveInputStream does not show location in file where a problem > occurred > > Seems to be fixed > > > Agreed (with the "seems to be fixed" part). > > > > COMPRESS-113 > > TarArchiveEntry.parseTarHeader() includes the trailing space/NUL when > > parsing the octal > > Suggestion from Sebb available. If a trailing NUL is in the tar specs, > > I wold go for option 2 otherwise 1. > > > If only there was *the* tar spec. The best source I know is the FreeBSD > man page > > <http://www.freebsd.org/cgi/man.cgi?query=tar&sektion=5&manpath=FreeBSD+8-current> > and it says "must end in a space" for 'old archives' and "allows > [numeric fields] to be terminated with either space or NUL". Similar > rules (slightly twisted for 'old archives') apply to other fields than > size as well, like mode or uid. > > I'd go with "insist on a trailing space or NUL". > > > > COMPRESS-18 > > JarArchiveEntry does not populate manifestAttributes or certificates > > I undestood this one has been solved in another way from Stefan > > > If we decided to adopt the patch it would need some additional work to > update the byte count, no biggie but that would delay the release > further. We could as well move the issue to 1.2. > > > > Then we can finally go on with C1.1 :-)
What about COMPRESS-108 - Command-line interface? Any objections if I add it to SVN, and change the pom to define it as the Main-Class? S/// --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
