[ 
https://issues.apache.org/jira/browse/CASSANDRA-14667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17764307#comment-17764307
 ] 

Stefan Miklosovic commented on CASSANDRA-14667:
-----------------------------------------------

1.7.25 is version of slf4j-api, log4j-over-slf4j and jcl-over-slf4j.

1.2.9 is version of logback-core and logback-classic. Is not that a different 
thing?

TBH I feel a little bit uneasy about bumping 1.2.9 to 1.4.11 (latest stuff for 
logback-core afaik). I think it is way more easier to just bump a patch version 
from 1.2.9 to 1.2.12 rather than "testing if dropwizard works with 1.4.11". 
What does even "to test" mean in this context?

We can contemplate about bumping it to 1.4.11 some other time, let's just bump 
it to 1.2.11 so Dropwizard do not pull that and that's it.

> Upgrade Dropwizard Metrics to 4.x
> ---------------------------------
>
>                 Key: CASSANDRA-14667
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-14667
>             Project: Cassandra
>          Issue Type: Task
>          Components: Observability/Metrics
>            Reporter: Stig Rohde Døssing
>            Assignee: Maxim Muzafarov
>            Priority: Normal
>             Fix For: 5.x
>
>         Attachments: signature.asc, signature.asc
>
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> Cassandra currently uses Metrics 3.1.5. Version 4.0.0 added some fixes for 
> Java 9 compatibility. It would be good to upgrade the Metrics library as part 
> of the version of Cassandra that adds Java 9 compatibility 
> (https://issues.apache.org/jira/browse/CASSANDRA-9608). 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to