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 are the good boys that have already been convinced:
http://repo1.maven.org/maven2/org/apache/commons/
Please consider this for the next release.
This was up on the table for this release, but we decided against it.
The reasons can be found in the mail-archive, if you look back far
enough. The main reason is that it's a point release. It should be a
drop-in replacement.
If there comes a 1.2 or 2.0 release I'm sure we'll address it.
BTW: it is then still possible to add backward ports to relocate
people that have NOT fixed their groupId so nobody gets lost.
Unfortunately it's not all that easy to do. No matter which way you look
at it, there are always some drawback when changing the groupId. Doing
it anyway is possibly dangerous because of the widespread use
commons-logging has.
Thanks a lot
Jörg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHWI0cmPuec2Dcv/8RAosFAJ0UsByrldFWdluML+IpxX76IIWiXACffDAT
SWvqyrK1ZZq5CcLcKYwmsVY=
=kCY7
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
