commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Torsten Curdt (JIRA)" <>
Subject [jira] [Commented] (COMPRESS-328) TarArchiveEntry preserveLeadingSlashes has no effect on setName
Date Fri, 15 Jan 2016 13:49:39 GMT


Torsten Curdt commented on COMPRESS-328:

Cool - then I'll commit the changes as outlined in 2) and add it to the release notes.

As for the {{setName}}: Imagine reading a {{TarArchiveEntry}} and writing it out to another
archive - and in the process renaming the entries. You could create a new {{TarArchiveEntry}}
to write from the {{TarArchiveEntry}} read - or mutate the one read. The {{setName}} use case
is the latter.

> TarArchiveEntry preserveLeadingSlashes has no effect on setName
> ---------------------------------------------------------------
>                 Key: COMPRESS-328
>                 URL:
>             Project: Commons Compress
>          Issue Type: Improvement
>            Reporter: Torsten Curdt
>            Priority: Minor
> We've run into an inconsistency with the TarArchiveEntry at jdeb.
> You can create a `TarArchiveEntry(String name, boolean preserveLeadingSlashes)` but the
`preserveLeadingSlashes` is only applied in the constructor.
> I am proposing to turn `preserveLeadingSlashes` into a read-only property and use the
value on `setName()`, too (instead of just false).
> This has some implications and maybe some backwards compatibility issues - but even then
I think it would be the right thing to do.
> I am happy to make the change but thought to discuss this first.

This message was sent by Atlassian JIRA

View raw message