commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Grobmeier <>
Subject [compress] ArArchiver Implementation strange behaviour
Date Sat, 28 Feb 2009 11:32:49 GMT

when working on the Testcases i figured out that a deletion from an Ar
Archive is not as successful as it look at first glance.
For example: my file contains test1.xml and test2.xml. I delete test2.xml

The "getNextEntry" Method just delivers test1.xml. Looks correct.

But checking the result file at commandline brings the following:

$> ar -t /tmp/dir26673/

vi shows me that there is still the test2.xml entry in the archive,
even when getNextEntry returns null.

Deleting test2.xml and adding test.txt afterward brings the following:

$> ar -t /tmp/dir24825/
ar: /tmp/dir24825/ Inappropriate file type or format

In ChangeSetTest are two cases at the bottom of the file with which
one can easily reproduce this issue (its applied in SANDBOX-183).

Torsten (or any other) if you can't check this out now I will create
an issue for that and check it out later. Let me know.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message