Mailing-List: contact users-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Users List" <users@maven.apache.org>
Received-SPF: pass (athena.apache.org: domain of
 gcjtmu-turbine-maven-user-846@m.gmane.org designates 80.91.229.2 as permitted
 sender)
To: users@maven.apache.org
From: =?UTF-8?B?SsO2cmc=?= Schaible <joerg.schaible@gmx.de>
Subject: Re: bug? strange resolution of commons-logging dependency
Date: Wed, 01 Jul 2009 08:21:35 +0200
Lines: 55
Message-ID: <h2ev6g$us8$1@ger.gmane.org>
References: <401a53e70906260946n2c92be8dqfce86e7e5d75e347@mail.gmail.com>
 <4A49BE5C.9070209@apache.org>
 <401a53e70906301249g19ba0be0g5dfc7939fe134d71@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8Bit
User-Agent: KNode/0.10.9
Sender: news <news@ger.gmane.org>

Lucas Bergman wrote at Dienstag, 30. Juni 2009 21:49:

> Dennis Lundberg wrote:
>> Lucas Bergman wrote:
>> > Running this test with Maven 2.1.0 fails:
>> >
>> >   java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory
>> >   [ ... ]
>> >
>> > The POM for htmlunit 2.5 declares commons-logging 1.1.1 as a
>> > (compile-scope) dependency, so this seems wrong.  There seems to
>> > be some interaction between that POM and the dependent POMs.
>> > Indeed:
>> >
>> >   [ ... ]
>> >
>> >   2.  Adding an exclusion of commons-logging to the
>> >   hibernate-ehcache dependency causes the test to succeed.  I
>> >   tried this, because the hibernate-ehcache POM depends on
>> >   commons-logging version 99.0-does-not-exist, a rather famous
>> >   JBoss kludge[1].
>> >
>> > [ ... ]
>> >
>> > Footnotes:
>> > [1] 
>> >
[http://day-to-day-stuff.blogspot.com/2007/10/announcement-version-99-does-not-exist.html
>>
>> That is your problem. What this does is mess the dependency-tree. It
>> removes commons-logging from the dependency tree because that
>> version "99.0-..." is larger than the latest current release of
>> commons-logging.  The "99.0-..." version should *never ever* reach
>> end users. It can *only* be used by internal project.
> 
> Thanks for the input.  Are you saying that the dependency of the
> hibernate-ehcache POM on commons-logging 99.0-does-not-exist is a bug?

It's an inappropriate solution for their problem with commons-logging.

> I'm sympathetic to that view, but I just want to be sure.  To be sure,
> it seems foolish for the Hibernate developers to put something like
> this in a library's POM, since it would seem to impose their kludge
> on the programmer using the library.

At least you should report this as a bug, since it actually breaks your
build. They should get at least aware or if.

> Of course, we fixed our particular problem by adding an <exclusion>
> for commons-logging from our hibernate-ehcache dependency.

You can declare commons-logging in a dependency management section. This
version and scope will have precedence over any transitive dep.

- Jörg


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org