[
https://jira.codehaus.org/browse/MNG-5510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354872#comment-354872
]
Shant Stepanian commented on MNG-5510:
--------------------------------------
Hi, can you please clarify what you mean by "forking the VM" here?
I don't see any fork option in the sonar plugin
(http://mojo.codehaus.org/sonar-maven-plugin/sonar-mojo.html), unlike say
maven-surefire-plugin
Is there another methodology you are considering here to fork?
> 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
> 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)
