Re: [compress] Planning 1.16 Release - With Source Incompatible Change

2018-01-28 Thread Bindul Bhowmik
Stefan, On Sun, Jan 28, 2018 at 4:08 AM, Stefan Bodewig wrote: > Hi all > > https://issues.apache.org/jira/projects/COMPRESS/versions/12341948 has a > nice set of new features and fixes and I'd like to cut a release > candidate the coming days. Not sure if this has anything to do with the recent

Re: [compress] TarArchiveEntry and Windows drive letter

2018-01-28 Thread Stefan Bodewig
On 2018-01-28, Torsten Curdt wrote: >>> This is what I suggested. Change the meaning of "preserveLeadingSlashes" >>> to "preserveAbsolutePath" and use it to keep the drive letter on >>> Windows. >>> The current code will always strip the drive letter spec. >> In that case, I agree with you. >>

Re: [compress] TarArchiveEntry and Windows drive letter

2018-01-28 Thread Torsten Curdt
> > This is what I suggested. Change the meaning of "preserveLeadingSlashes" > > to "preserveAbsolutePath" and use it to keep the drive letter on > > Windows. > > > > The current code will always strip the drive letter spec. > > In that case, I agree with you. > > Also as a name, 'preserveLeadingS

[compress] Planning 1.16 Release - With Source Incompatible Change

2018-01-28 Thread Stefan Bodewig
Hi all https://issues.apache.org/jira/projects/COMPRESS/versions/12341948 has a nice set of new features and fixes and I'd like to cut a release candidate the coming days. One thing I may want to do is to extend the "preserveLeadingSlashes" attribute of TarArchiveEntry to also preserve the drive