Joerg Hohwiller wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
...and we have a winner!
I am a little late ;)
Could you please change the groupId to "org.apache.commons.logging".
It is an ugly legacy problem that many projects are still ignoring the maven
conventions.
Here ar
Joerg Hohwiller <[EMAIL PROTECTED]> schrieb:
> Could you please change the groupId to "org.apache.commons.logging".
> It is an ugly legacy problem that many projects are still ignoring the maven
> conventions.
>
> Here are the good boys that have already been convinced:
> http://repo1.maven.o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
> ...and we have a winner!
I am a little late ;)
Could you please change the groupId to "org.apache.commons.logging".
It is an ugly legacy problem that many projects are still ignoring the maven
conventions.
Here are the good boys that have
...and we have a winner!
The vote has passed with the following votes:
+1 (binding): Torsten Curdt, Oliver Heger, Sebastian Bazley, Jörg
Schaible, Dennis Lundberg
+1 (non-binding at the time of his vote, but binding now): Ben Speakmon
+1 (non-binding): Nicolas de Loof,
I'm proceeding with t
+1
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 source and binary archives.
Release Notes:
h
On 24/11/2007, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
> sebb wrote:
> > On 23/11/2007, Oliver Heger <[EMAIL PROTECTED]> wrote:
> >> Dennis Lundberg wrote:
> >>> 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.
sebb wrote:
On 23/11/2007, Oliver Heger <[EMAIL PROTECTED]> wrote:
Dennis Lundberg wrote:
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
On 23/11/2007, Oliver Heger <[EMAIL PROTECTED]> wrote:
> Dennis Lundberg wrote:
> > 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
> >
I had a look in JIRA for the assembly plugin and found this issue:
http://jira.codehaus.org/browse/MASSEMBLY-222
It seems to fit the bill and is fixed in the 2.2-beta-2 release.
Ben Speakmon wrote:
Same thing (the 2.4-1 bit) happened to me when I was doing the email
release. I wasn't able to re
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 source and binary archives.
>
> R
Dennis Lundberg wrote:
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
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
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
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
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):
-
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
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
+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
+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
+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
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 source and binary archives.
Release Notes:
http://issues.apache.org/jira
21 matches
Mail list logo
