[
https://issues.apache.org/jira/browse/RAVE-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13240719#comment-13240719
]
Ate Douma commented on RAVE-529:
--------------------------------
This can easily be fixed already with the current shindig version and in way
which works too (and will be needed) when upgrading to shindig 2.5-beta1
The current rave-shindig is build using a war overlay on shindig-server.
As the shindig-server using slf4j 1.5.x as packaged in its WEB-INF/lib/ folder
it is simply a matter of adding an exclude on the war overlay configuration,
and add the needed slf4j version as rave-shindig dependency.
I also will add a slf4j-log4j12 dependency instead of the default
shindig-server packaged slf4j-jdk14 to keep it in line with rave-portal.
Finally, I noticed shindig-server also packages commons-logging which I'll also
exclude as we use jcl-over-slf4j in rave instead.
Once we upgrade to shindig 2.5-beta1 we no longer will need the shindig-server
war overlay and everything will become 'easy' ;)
> Move SLF4J to 1.6 after shindig re-org
> --------------------------------------
>
> Key: RAVE-529
> URL: https://issues.apache.org/jira/browse/RAVE-529
> Project: Rave
> Issue Type: Bug
> Reporter: Matt Franklin
> Assignee: Ate Douma
>
> Bump the SLF4J API back to 1.6 once the shindig changes in 2.5 beta 1 are in
> place.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
