[
https://issues.apache.org/jira/browse/CASSANDRA-15714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jon Meredith updated CASSANDRA-15714:
-------------------------------------
Fix Version/s: 4.0-alpha
Since Version: 4.0-alpha
Source Control Link:
https://gitbox.apache.org/repos/asf?p=cassandra-in-jvm-dtest-api.git;a=commit;h=7ddfe52d51639817c6c5be86c0c8e317e33620eba
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Not sure what version to set here as JIRA is based on main project versions,
not the dependency version - is really fixed in 0.0.2
> Support in cassandra-in-jvm-dtest-api for replacing logback with alternate
> logger
> ----------------------------------------------------------------------------------
>
> Key: CASSANDRA-15714
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15714
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest
> Reporter: Jon Meredith
> Assignee: Jon Meredith
> Priority: Normal
> Labels: pull-request-available
> Fix For: 4.0-alpha
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Not all forks use logback, and there is an (prematurely) closed ticket
> indicating that it would be valuable CASSANDRA-13212.
>
> Add support for making the log file configuration property and log file
> pathname configurable rather than hard-coding to logback.
>
> Also had to add 'org.w3c.dom' to the InstanceClassLoader so that log4j2 could
> load its configuration, but looks like that can be handled with the changes
> in CASSANDRA-15713
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
