[
https://jira.codehaus.org/browse/MNG-5510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348152#comment-348152
]
Jason van Zyl commented on MNG-5510:
------------------------------------
Yes, I know what the issue is. If a host project hard codes an implementation
there are going to be issues running from Maven. So your option is to fork for
now as I'm not looking at fixing this anytime soon.
> Maven causing ClassCastException with container plugins when project is using
> other SLF4J implementation than slf4j-simple
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: MNG-5510
> URL: https://jira.codehaus.org/browse/MNG-5510
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Bootstrap & Build, Logging
> Affects Versions: 3.1.0
> Reporter: Juan Pablo Santos RodrÃguez
> Attachments: MNG-5510-sample.zip
>
>
> On our project we're using directly logback to start up a custom mbean to be
> able to change log levels dynamically, among other things. Most of these
> operations are Logback-specific, they're not available via SLF4J API
> For testing we use Jetty, so when we're doing an mvn jetty:run, the mbean
> gets init'd and we get an Exception stating "ClassCastException:
> org.slf4j.impl.SimpleLoggerFactory cannot be cast to
> ch.qos.logback.classic.LoggerContext", due to slf4j-simple being on maven's
> lib. This is very likely to happen with other container plugins (tomcat7 et
> al)
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
