maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Juan Pablo Santos Rodríguez (JIRA) <j...@codehaus.org>
Subject [jira] (MNG-5510) Maven causing ClassCastException with container plugins when project is using other SLF4J implementation than slf4j-simple
Date Mon, 16 Jun 2014 07:28:10 GMT

     [ https://jira.codehaus.org/browse/MNG-5510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Juan Pablo Santos Rodríguez updated MNG-5510:
---------------------------------------------

    Attachment: MNG-5510-sample.zip

sample project with instructions to reproduce the issue

> 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)

Mime
View raw message