Re: [compress] release for Zstandard?

2017-12-23 Thread Stefan Bodewig
On 2017-12-22, Gary Gregory wrote: > When can we get a [compress] release? It would be nice to get Zstandard out > there. It's incomplete as it is read-only and adding write support would be as trivial as adding read-only support has been. It's only a matter of finding tme to do

[compress] release for Zstandard?

2017-12-22 Thread Gary Gregory
When can we get a [compress] release? It would be nice to get Zstandard out there. Gary

Re: [compress] release?

2016-12-09 Thread Stefan Bodewig
On 2016-12-09, Gary Gregory wrote: > Just FWIW, we fail on Java 9 with: > Failed tests: > X5455_ExtendedTimestampTest.testSampleFile:185 > expected:<[2105-01-01/00:00:02] +> but was:<[1968-11-24/17:31:45] +> > Tests in error: > SevenZNativeHeapTest.initializationError » Objenesis > ja

Re: [compress] release?

2016-12-09 Thread Stefan Bodewig
On 2016-12-09, Gary Gregory wrote: > On Thu, Dec 8, 2016 at 9:19 PM, Stefan Bodewig wrote: >> On 2016-12-09, Gary Gregory wrote: >>> What is the outlook on a release? I'd like to make use of >>> in LZMACompressorOutputStream. >> There are two unresolved issues assigned to 1.13. No idea who ass

Re: [compress] release?

2016-12-09 Thread Gary Gregory
Just FWIW, we fail on Java 9 with: Failed tests: X5455_ExtendedTimestampTest.testSampleFile:185 expected:<[2105-01-01/00:00:02] +> but was:<[1968-11-24/17:31:45] +> Tests in error: SevenZNativeHeapTest.initializationError » Objenesis java.lang.reflect.Invocat... Tests run: 613, Failur

Re: [compress] release?

2016-12-09 Thread Gary Gregory
On Thu, Dec 8, 2016 at 9:19 PM, Stefan Bodewig wrote: > On 2016-12-09, Gary Gregory wrote: > > > What is the outlook on a release? I'd like to make use of > > in LZMACompressorOutputStream. > > There are two unresolved issues assigned to 1.13. No idea who assigned > them but it would be good if w

Re: [compress] release?

2016-12-08 Thread Stefan Bodewig
On 2016-12-09, Gary Gregory wrote: > What is the outlook on a release? I'd like to make use of > in LZMACompressorOutputStream. There are two unresolved issues assigned to 1.13. No idea who assigned them but it would be good if who ever did it could look into them: https://issues.apache.org/jira

[compress] release?

2016-12-08 Thread Gary Gregory
Hi devs, What is the outlook on a release? I'd like to make use of in LZMACompressorOutputStream. Gary -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition

Re: [compress] Release - last steps

2010-08-21 Thread sebb
I've raised the issue with Infra. On 21 August 2010 08:33, Christian Grobmeier wrote: > Still no sync... but good it mades its way already to some US servers. > Maybe on monday situation has changed... > >> Strange. >> >> Has not even made it to the EU mirror: >> >> http://www.eu.apache.org/dist/

Re: [compress] Release - last steps

2010-08-21 Thread Christian Grobmeier
Still no sync... but good it mades its way already to some US servers. Maybe on monday situation has changed... > Strange. > > Has not even made it to the EU mirror: > > http://www.eu.apache.org/dist/commons/compress/binaries/ > > This means no European mirrors will have the files, as they should

Re: [compress] Release - last steps

2010-08-20 Thread sebb
On 20 August 2010 05:55, Christian Grobmeier wrote: >>> I will check and send announcement a little later > > Mirrors have not synced up - I will some more time. Strange. Has not even made it to the EU mirror: http://www.eu.apache.org/dist/commons/compress/binaries/ This means no European mirr

Re: [compress] Release - last steps

2010-08-19 Thread Christian Grobmeier
>> I will check and send announcement a little later Mirrors have not synced up - I will some more time. > And a day or so after that, please delete the old 1.0 release files from > dist/*. Will do, thanks Sebb Christian >> On Thu, Aug 19, 2010 at 8:17 AM, Christian Grobmeier >> wrote: >>>

Re: [compress] Release - last steps

2010-08-19 Thread sebb
On 19 August 2010 07:23, Christian Grobmeier wrote: > Site looks better now :-) That will be the synch delay. > I will check and send announcement a little later And a day or so after that, please delete the old 1.0 release files from dist/*. > On Thu, Aug 19, 2010 at 8:17 AM, Christian Grobme

Re: [compress] Release - last steps

2010-08-18 Thread Christian Grobmeier
Site looks better now :-) I will check and send announcement a little later On Thu, Aug 19, 2010 at 8:17 AM, Christian Grobmeier wrote: > Just have uploaded artifacts and released it from nexus. > http://www.apache.org/dist/commons/compress/ > > Site is already uploaded with mvn site:deploy > It

[compress] Release - last steps

2010-08-18 Thread Christian Grobmeier
Just have uploaded artifacts and released it from nexus. http://www.apache.org/dist/commons/compress/ Site is already uploaded with mvn site:deploy It looks strange - have checked the upload on people/3/c.a.o/compress but it looks like it is still the old content, even when my mvn goal was success

Re: [compress] release 1.1?

2010-08-03 Thread Torsten Curdt
>> Hm ...lots of stuff in there. > > That's why you need more than a C short to cover everything 8-) :-D >> But looks reasonable.  Should be all "boolean"s instead of some >> "Boolean"s thought, right? > > Boolean was intentional since ZIP doesn't have any idea whether an entry > is a regular fil

Re: [compress] release 1.1?

2010-08-02 Thread Stefan Bodewig
On 2010-08-02, Torsten Curdt wrote: >> class PosixAttributes { >>    /* nine constants */ >>    static final int OWNER_CAN_READ = ... >>    /* set of the constants that apply */ >>    Set getPermissions(); >>    /* could be mixed with permissions if we wanted to */ >>    Boolean isSetUserId(); >

Re: [compress] release 1.1?

2010-08-02 Thread Torsten Curdt
> Just tossing out ideas > > class OwnerInformation { >    int getUserId(); >    int getGroupId(); >    String getUserName(); >    String getGroupName(); > } > > class ArchiveEntry { >    OwnerInformation getOwner(); > } > > ZIP would return null on getOwner, AR and CPIO return null in the *Name >

Re: [compress] release 1.1?

2010-08-02 Thread Torsten Curdt
>> Unless there's already a ready patch for this, I'd rather see the 1.1 >> release out than wait for a new improvement. > > +1 It certainly should not block the release. > We'll probably take longer defining the API than implementing it, though > 8-) Yeah :) > I agree that 1.1 is overdue, ther

Re: [compress] release 1.1?

2010-08-02 Thread Stefan Bodewig
On 2010-08-02, Jukka Zitting wrote: > Hi, > On Tue, Jul 20, 2010 at 10:57 AM, Torsten Curdt wrote: >> ...maybe then there is one more thing to squeeze in then > Unless there's already a ready patch for this, I'd rather see the 1.1 > release out than wait for a new improvement. +1 We'll probab

Re: [compress] release 1.1?

2010-08-02 Thread Jukka Zitting
Hi, On Tue, Jul 20, 2010 at 10:57 AM, Torsten Curdt wrote: > ...maybe then there is one more thing to squeeze in then Unless there's already a ready patch for this, I'd rather see the 1.1 release out than wait for a new improvement. BR, Jukka Zitting --

Re: [compress] release 1.1?

2010-07-23 Thread Stefan Bodewig
On 2010-07-22, Torsten Curdt wrote: >> Between 1.0 and 1.1 I pushed getLastModifiedDate into ArchiveEntry to >> simplify a very common case. > Maybe we should add some more there. >>> If a particular ArchiveEntry doesn't support e.g. getGroup() it would >>> just return null ...but I am a little

Re: [compress] release 1.1?

2010-07-22 Thread Torsten Curdt
>> 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 > Exactly ...and look how s

Re: [compress] release 1.1?

2010-07-21 Thread Stefan Bodewig
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 prope

Re: [compress] release 1.1?

2010-07-21 Thread Torsten Curdt
>> Especially as there should be a limit of what you can expect/express. >> After all it describes a file with it's metadata. In theory >> ArchiveEntry could be the superset of all that's there. Looking at the >> various implementations this doesn't seem to be too far fetched. If a >> particular Ar

Re: [compress] release 1.1?

2010-07-21 Thread Christian Grobmeier
> ...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 ;-) Thanks that I am lying in the sun while thinking about your suggestion ;-) > whenever one want to get to the properties of an ArchiveEntry one has >

Re: [compress] release 1.1?

2010-07-20 Thread Torsten Curdt
...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 ;-) I was thinking... whenever one want to get to the properties of an ArchiveEntry one has to figure out what actual implementation it is. This kind of sucks

Re: [compress] release 1.1?

2010-07-19 Thread Christian Grobmeier
Same to me - Stefan and I will coop after the holiday for getting this release done. On Tue, Jul 20, 2010 at 6:53 AM, Stefan Bodewig wrote: > On 2010-07-19, Torsten Curdt wrote: > >> Ups - thought we already released it!? What about a release now-ish? > > +1 in general, but I'll be on vacation un

Re: [compress] release 1.1?

2010-07-19 Thread Stefan Bodewig
On 2010-07-19, Torsten Curdt wrote: > Ups - thought we already released it!? What about a release now-ish? +1 in general, but I'll be on vacation until end of July with only random internet access (like just now 8-) so won't be much help over the next two weeks. Stefan -

[compress] release 1.1?

2010-07-19 Thread Torsten Curdt
Ups - thought we already released it!? What about a release now-ish? I looked through the open issues and I don't think I see any blockers. There is always one more bug ...but there can always be one more release, too. cheers -- Torsten ---