You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Doug Rohrer (Jira)" <ji...@apache.org> on 2025/10/09 18:13:00 UTC
[jira] [Updated] (CASSANDRA-20884) Move JMX classes to the in-jvm-dtest API project and other small dtest-api improvements
[ https://issues.apache.org/jira/browse/CASSANDRA-20884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Doug Rohrer updated CASSANDRA-20884:
------------------------------------
Attachment: ci_summary-4.0.html
ci_summary-4.1.html
ci_summary-5.0.html
ci_summary-trunk.html
> Move JMX classes to the in-jvm-dtest API project and other small dtest-api improvements
> ---------------------------------------------------------------------------------------
>
> Key: CASSANDRA-20884
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20884
> Project: Apache Cassandra
> Issue Type: Task
> Components: Test/dtest/java
> Reporter: Doug Rohrer
> Assignee: Doug Rohrer
> Priority: Normal
> Attachments: ci_summary-4.0.html, ci_summary-4.1.html, ci_summary-5.0.html, ci_summary-trunk.html
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> Several important JMX-related test classes should be moved over from the Cassandra codebase to the in-jvm-dtest library for two reasons:
> 1) They are duplicated in every Cassandra version from 4.0 onwards, and don't need to be.
> 2) More imporantly, using these classes outside of the Cassandra project (in sidecar and analytics) requires that those projects also have access to these classes, and we've worked around this with some fairly ugly hacks (copy/paste of code across even more projects) to date. Moving these will eliminate the need for the hacks.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org