> > It is not the job of commons-compress to stop you from using a > corrupt archive. If you choose to do so, then ... >
I don't think that's what it is. That would be more like getting an exception and continuing walking through the archive. If there is a parse exception there is a bug in the input. If there is runtime exception there is a bug in the code. If the user does a try/catch for a runtime exception there is no indication which of the two it is. I personally find it a shame if we were to blur those lines.
