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 Mon, 12 Nov 2007 21:31:11 GMT
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.

Steve Loughran wrote:
> On Nov 12, 2007 2:33 PM, Brett Porter <brett@apache.org> wrote:
>> Are you asking the right list?
>> - Brett
> well, I think I should submit the bug report "log4j 1.2.15 introduces
> bad dependencies" to the log4j, team, but I was surprised that such a
> mainstream artifact did manage to get the metadata in there with a
> dependency on artifacts that dont exist. It's clearly bad repository
> metadata that should never have got in there.
> It makes me think that part of the repository checking ought to
> include a warning if a release of an artifact suddenly adds new
> dependencies, as a "review this change" kind of event.
>> On 12/11/2007, at 8:59 AM, Steve Loughran wrote:
>>> http://repo1.maven.org/maven2/log4j/log4j/1.2.15/log4j-1.2.15.pom
>>> note the non-optional dependencies on javax.mail, javax.jms, and
>>> com.sun.jmdk jmxri. There are not in the central repo.
>>> If you try and use log4j 1.2.15 you not get stuff you dont want (at
>>> best) or your build breaks (at worst). This is not a good advert for
>>> the repository; I cant increment my properties file and expect things
>>> to work, not without finding everywhere that I use log4j and turning
>>> off dependencies (which may be a good thing, but I am not happy its
>>> forced in)
>>> -steve
>> --
>> Brett Porter - brett@apache.org
>> Blog: http://www.devzuz.org/blogs/bporter/

Dennis Lundberg

View raw message