|
||||||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||||||
- [mojo-dev] [jira] (MCASSANDRA-25) Logging configur... Mikhail Mazursky (JIRA)
- [mojo-dev] [jira] (MCASSANDRA-25) Logging con... Stephen Connolly (JIRA)
- [mojo-dev] [jira] (MCASSANDRA-25) Logging con... Mikhail Mazursky (JIRA)
- [mojo-dev] [jira] (MCASSANDRA-25) Logging con... Mikhail Mazursky (JIRA)
- [mojo-dev] [jira] (MCASSANDRA-25) Logging con... Mikhail Mazursky (JIRA)
- [mojo-dev] [jira] (MCASSANDRA-25) Logging con... Olivier Lamy (JIRA)
- [mojo-dev] [jira] (MCASSANDRA-25) Logging con... Olivier Lamy (JIRA)

Attaching proposed patch.
1. Removed slf4j-api and jcl-over-slf4j exclusions because the are needed for logging.
2. Added exclusion for commons-logging and added jcl-over-slf4j instead of it.
3. Added exclusion for slf4j-log4j12 and log4j.
4. slf4j-api version is managed to be the same as of jcl-over-slf4j.
With that modifications all logging from cassandra and all it's dependencies will go to slf4j API. If user wants to see logs he have to add a slf4j binding as a plugin dependency and configure it. That can be log4j, logback, etc.