www-repository mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dennis Lundberg <denn...@apache.org>
Subject Re: wtf happened to log4j?
Date Wed, 14 Nov 2007 15:59:07 GMT
Steve Loughran wrote:
> On Nov 12, 2007 9:31 PM, Dennis Lundberg <dennisl@apache.org> wrote:
>> I think that the 1.2.15 release is the first Maven 2 release of log4j.
>> Perhaps we can offer them some help in getting their pom corrected.
> Looks like they've noticed
> http://issues.apache.org/bugzilla/show_bug.cgi?id=43304
> but they need some consultancy to differentiate what is non-optional
> to build log4j (their problem) with what is needed to run it (everyone
> else's).

I'll see if I can help out.

> Regardless of whose fault it is, its a strong argument against using
> transitive dependency info from any third party project, no matter
> which tool you use. Because you can't be sure that a point increment
> wont introduce some version of something you don't want. I'm going to
> have to go through all my ivy.xml files that use log4j and make sure I
> only ask for the artifact itself, same as we do for commons-logging.

Agreed, but I'm sure it was unintentional. Just hold back on upgrading 
log4j until a fixed version comes out. Unless of course there is 
something in 1.2.15 that you absolutely need.

Give me one more week and I hope to have commons-logging-1.1.1 out the 
door. ;-)

> this whole thing is pretty messy. Still, my dependency metadata will
> be more robust, once I have revised it.
> -steve

Dennis Lundberg

View raw message