[
https://jira.codehaus.org/browse/MNG-5101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=283344#comment-283344
]
Anthony Whitford commented on MNG-5101:
---------------------------------------
Noting this workaround: http://www.slf4j.org/faq.html#excludingJCL
and: http://day-to-day-stuff.blogspot.com/2007/07/no-more-commons-logging.html
> Declare artifact is a replacement to avoid excessive exclusions
> ---------------------------------------------------------------
>
> Key: MNG-5101
> URL: https://jira.codehaus.org/browse/MNG-5101
> Project: Maven 2 & 3
> Issue Type: Wish
> Components: Dependencies
> Affects Versions: 2.2.1
> Reporter: Anthony Whitford
> Priority: Minor
>
> For those of us using something like [SLF4J|http://slf4j.org/] and including
> a [legacy API bridge|http://slf4j.org/legacy.html] like {{jcl-over-slf4j}}
> as a replacement to {{commons-logging}}, it would be nice to be able to have
> the {{jcl-over-slf4j}} artifact declare in its POM that it is a logical
> replacement to {{commons-logging}}, so that one can avoid the excessive
> {{<exclusions>}} for the numerous artifacts that still reference the legacy
> api:
> {code}
> <exclusions>
> <exclusion>
> <groupId>commons-logging</groupId>
> <artifactId>commons-logging</artifactId>
> </exclusion>
> </exclusions>
> {code}
> One work-around that one can use is to declare {{commons-logging}} as
> {{provided}} in a project's pom -- but then it appears in the dependency
> tree, which is not really nice.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
