www-repository mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carlos Sanchez" <car...@apache.org>
Subject Re: wtf happened to log4j?
Date Wed, 14 Nov 2007 01:25:52 GMT
that's only a problem when you upgrade,same thing if they decide to
break the api or do something goofy with the code

On Nov 14, 2007 4:34 AM, Steve Loughran <steve.loughran@gmail.com> 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).
> 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.
> this whole thing is pretty messy. Still, my dependency metadata will
> be more robust, once I have revised it.
> -steve

I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
                             -- The Princess Bride

View raw message