one more thing I discovered: In update mode it has always been possible that we replace a given ZipEntry with an older version as we add all "included files" from the filesets, without checking whether they are really newer (the test is only used to determine whether the archive should be updated or not).
With the old code, this scenario is pretty unlikely as that would imply ZipEntrys of the archive to update having a newer date than the date of the archive itself, but with the new code, this is likely to happen. I'll try to fix this (again, trying to find time to write the tests first), but it will mean we need even more reshuffling in Zip to make it work at a reasonable speed. Stefan -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
