commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Bodewig <>
Subject Re: [compress] release 1.1?
Date Thu, 22 Jul 2010 04:21:39 GMT
On 2010-07-20, Torsten Curdt wrote:

> ...maybe then there is one more thing to squeeze in then
> ...or at least start the discussion so you can think about while lying
> in the sun ;-)

In my case it's more like herding cats, err, kids.

> I was thinking...

> whenever one want to get to the properties of an ArchiveEntry one has
> to figure out what actual implementation it is.

I know what you mean

Between 1.0 and 1.1 I pushed getLastModifiedDate into ArchiveEntry to
simplify a very common case.

> If a particular ArchiveEntry doesn't support e.g. getGroup() it would
> just return null ...but I am a little back and forth on this. Mostly
> because of methods returning primitives

I solved this by returning Interger.MIN_VALUE - the group id should
never be < 0 anyway.

> ...and the bloat of the interface.

That's been my main concern as well and that's why I stopped with the
last modified date.

All four archive implementations of trunk support file permissions and
use something like the Unix stat structure which means they are at least
interchangeable (cpio actually returns a long but the value will never
be outside the scope of an int).  At some point in time I thought about
unifying it (and move the UnixStat helper from the ZIP package somewhere
more accessible) but think I deferred it because I considered the 1.1
release to be too close - and forgot about it later.

All but ZIP allow access to the numeric group and user ids.  I don't
think they share anything else.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message