commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jörg Schaible <joerg.schai...@gmx.de>
Subject Re: sanctioning commons-logging version "99.0-does-not-exist"
Date Thu, 14 May 2009 09:41:04 GMT
sebb wrote at Donnerstag, 14. Mai 2009 11:35:

> On 14/05/2009, Ceki Gulcu <ceki@qos.ch> wrote:
>> Hello all,
>>
>>  A large number of Maven projects declare commons-logging as a
>>  dependency. Thus, if a developer wishes to use jcl-over-slf4j instead
>>  of commons-logging, he or she would need to declare a commons-logging
>>  exclusion in all of his/her dependencies which transitively depend on
>>  commons-logging. This can be an error prone process. To alleviate the
>>  pain, Erik van Oosten has developed a clever hack around this problem.
>>
>>  See http://tinyurl.com/2kds3v for details.
>>
>>  The idea is to publish empty artifacts which supposedly fulfill
>>  dependencies for commons-logging without actually providing any
>>  classes (hence the empty artifacts).
>>
>>  This approach works fine except that it requires the declaration of a
>>  new repository in the project's pom.xml file. Moreover, the durability
>>  of this repository is also questionable.
> 
> Has anyone tried declaring commons logging as <scope>system</scope> ?
> 
> Won't that stop it being added to the classpath?

Use scope "provided" - if any. Actually if people use a master pom and
declare CL in the depMgmt section with this scope, it should do the trick.

- Jörg


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message