www-repository mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran" <steve.lough...@gmail.com>
Subject Re: wtf happened to log4j?
Date Wed, 28 Nov 2007 00:37:04 GMT
On Nov 27, 2007 9:06 PM, Curt Arnold <carnold@apache.org> wrote:
> We were quickly notified that updating log4j 1.2.15 had the
> unfortunate side effect of propagating non-redistributable artifacts
> to dependent projects.   Those artifacts are necessary to build log4j,
> but not necessary to run log4j unless you use specific features.
> We've marked those dependencies as optional in our SVN HEAD's pom.xml (http://svn.apache.org/repos/asf/logging/log4j/trunk/pom.xml
> ) and expect to push out a 1.2.16 in the near future.

oh, it happens :).  The fact that so many people noticed is a metric
of success.

Thank you for fixing it.

> There was a suggestion to scope the dependencies as "provided" since
> if those features were used, it would generally (but not exclusively)
> be in a J2EE environment where the dependencies would be part of the
> J2EE classpath.  However, that seems wrong based on my reading.
> If you have any advice on the log4j 1.2.16 pom.xml, please post to
> log4j-dev.  Thanks.

Best to let maven people review it fully, though I will try it out
against ivy to see what it makes of it.


View raw message