Re: [compress] Tar stream signature detection regression as of 1.11

According to git bisect, 1fb42987de0d21c9b6777272320b64230eadb277 is the first bad commit commit 1fb42987de0d21c9b6777272320b64230eadb277 Author: Stefan Bodewig Date: Sun Jan 31 13:12:31 2016 +0100 COMPRESS-331 make tar checksum check as strict as GNU tar On Thu,

Re: [ALL] Automated requirements (e.g. CheckStyle)?

On Wed, 9 Aug 2017 10:56:47 +0100, sebb wrote: On 9 August 2017 at 03:57, Gilles wrote: On Tue, 8 Aug 2017 18:49:44 -0700, Chas Honton wrote: Since most of us work in an IDE, the "wasted" time of checkstyle for every build is negligible. IDEs vary in how

[compress] Tar stream signature detection regression as of 1.11

Hello, I think I may have found a regression in ArchiveFormatFactory.createArchiveInputStream. Please run the JUnit testcase at the end of this mail. It demonstrates the archive detection working with 1.10, but failing from 1.11 through 1.14 The file "COMPRESS-117.tar" is taken from