[CASSANDRA-15714] Support in cassandra-in-jvm-dtest-api for replacing logback with alternate logger

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 4.0-beta1, 4.0
• Component/s: Test/dtest/java
• Labels: pull-request-available
• Bug Category: Code
• Severity: Low
• Complexity: Low Hanging Fruit
• Discovered By: Unit Test
• Platform: All
• 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

Test and Documentation Plan

Manual check it worked in upstream build.

• Assignee: Jon Meredith
• Reporter: Jon Meredith

Authors

Jon Meredith

Reviewers

David Capwell

• Created: 10/Apr/20 22:31
• Updated: 21/Dec/20 08:08
• Resolved: 20/Apr/20 15:53

Description

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

Issue Links

• relates to: CASSANDRA-15713 InstanceClassLoader fails to load with the following previously initiated loading for a different type with name "org/w3c/dom/Document"
• links to: GitHub Pull Request #8