Re: [VOTE] Release commons-logging 1.1.1 (take 4)

2007-11-22 Thread Ben Speakmon
Same thing (the 2.4-1 bit) happened to me when I was doing the email release. I wasn't able to repro it, so I didn't file a bug and wrote it off to cosmic rays. But obviously there's something strange going on. +1 nonbinding on the release, BTW. On Nov 22, 2007 1:54 PM, Dennis Lundberg <[EMAIL PR

Re: [VOTE] Release commons-logging 1.1.1 (take 4)

2007-11-22 Thread Dennis Lundberg
Yeah, I just noticed that as well. WTF! I am unable to reproduce it again, even with an exact copy of the files I built before. This is just the source distributions though, so no jars are present in them. Would it be OK if I repackage the -src.zip and -src.tar.gz files with the correct path a

Re: [VOTE] Release commons-logging 1.1.1 (take 4)

2007-11-22 Thread Dennis Lundberg
Oliver Heger wrote: Dennis Lundberg wrote: Oliver Heger wrote: +1 Some minor remarks (which are not too problematic IMO): - The format of the md5 files is a bit unusual. Other components typically use a format like f88520ed791673aed6cc4591bc058b55 *commons-logging-1.1.1-bin.zip I created

Re: [VOTE] Release commons-logging 1.1.1 (take 4)

2007-11-22 Thread Oliver Heger
Sorry, just noticed one more thing: The source distributions unpack in a directory "commons-logging-2.4.1-src". This version number is really future-proof ;-) Oliver Oliver Heger wrote: Dennis Lundberg wrote: Oliver Heger wrote: +1 Some minor remarks (which are not too problematic IMO): -

Re: [VOTE] Release commons-logging 1.1.1 (take 4)

2007-11-22 Thread Oliver Heger
Dennis Lundberg wrote: Oliver Heger wrote: +1 Some minor remarks (which are not too problematic IMO): - The format of the md5 files is a bit unusual. Other components typically use a format like f88520ed791673aed6cc4591bc058b55 *commons-logging-1.1.1-bin.zip I created them on people.a.o af

Re: [VOTE] Release commons-logging 1.1.1 (take 4)

2007-11-22 Thread Dennis Lundberg
Oliver Heger wrote: +1 Some minor remarks (which are not too problematic IMO): - The format of the md5 files is a bit unusual. Other components typically use a format like f88520ed791673aed6cc4591bc058b55 *commons-logging-1.1.1-bin.zip I created them on people.a.o after uploading the files

Re: [VOTE] Release commons-logging 1.1.1 (take 4)

2007-11-22 Thread Oliver Heger
+1 Some minor remarks (which are not too problematic IMO): - The format of the md5 files is a bit unusual. Other components typically use a format like f88520ed791673aed6cc4591bc058b55 *commons-logging-1.1.1-bin.zip - When building the source distribution with maven2 LICENSE and NOTICE are n

Re: [VOTE] Release commons-logging 1.1.1 (take 4)

2007-11-22 Thread Torsten Curdt
+1 cheers -- Torsten On 22.11.2007, at 00:37, Dennis Lundberg wrote: Hi This is the fourth attempt to release commons-logging 1.1.1. Changes since the last go: - The manifests now has the correct X-Compile-Target-JDK in them - The manifests no longer mention Jakarta - [LOGGING-118] Generate

Re: [VOTE] Release commons-logging 1.1.1 (take 4)

2007-11-22 Thread nicolas de loof
+1 2007/11/22, Dennis Lundberg <[EMAIL PROTECTED]>: > > Hi > > This is the fourth attempt to release commons-logging 1.1.1. > > Changes since the last go: > - The manifests now has the correct X-Compile-Target-JDK in them > - The manifests no longer mention Jakarta > - [LOGGING-118] Generate sourc