[
https://issues.apache.org/jira/browse/CASSANDRA-12996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16099854#comment-16099854
]
Stefan Podkowinski commented on CASSANDRA-12996:
------------------------------------------------
[~jay.zhuang] that's a good point. I imaging that we could use the maven
dependency resolver for that as well and have it populate the lib folder. But
removing binary dependencies from the repo needs its own discussion I think and
is out of scope for this ticket.
Latest patch has now been merged as 481e6003461d0e94f.
I hope we don't have to roll back because of CASSANDRA-13723. But never
upgrading slf4j isn't a solution and migrating to another logging framework
probably won't happen as well. So we have to bite the bullet here and do some
log messages cleanup, I'm afraid.
> update slf4j dependency to 1.7.21
> ---------------------------------
>
> Key: CASSANDRA-12996
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12996
> Project: Cassandra
> Issue Type: Improvement
> Components: Libraries
> Reporter: Tomas Repik
> Assignee: Stefan Podkowinski
> Fix For: 4.0
>
> Attachments: cassandra-3.11.0-slf4j.patch,
> jcl-over-slf4j-1.7.25.jar.asc, log4j-over-slf4j-1.7.25.jar.asc,
> slf4j-api-1.7.25.jar.asc
>
>
> Cassandra 3.11.0 is about to be included in Fedora. There are some tweaks to
> the sources we need to do in order to successfully build it. Cassandra
> depends on slf4j 1.7.7, but In Fedora we have the latest upstream version
> 1.7.21 It was released some time ago on April 6 2016. I attached a patch
> updating Cassandra sources to depend on the newer slf4j sources. The only
> actual change is the number of parameters accepted by SubstituteLogger class.
> Please consider updating.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
