[CASSANDRA-15489] Allow dtest jar directory to be configurable

• Type: Improvement
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 2.2.16, 3.0.20, 3.11.6, 4.0, 4.0-alpha3
• Component/s: Test/dtest/java
• Labels: pull-request-available
• Change Category: Operability
• Complexity: Low Hanging Fruit
• Platform: All

Source Control Link

https://github.com/apache/cassandra/commit/37828ee05cb622caaf7366a7cd550544f6cdc14b

Test and Documentation Plan

This will allows things like CI systems and external consumers of the dtest framework to leverage upgrade tests without having to jump through too many hoops. Tested that it didn’t break existing functionality by running upgrade tests without changing the property.

• Assignee: Doug Rohrer
• Reporter: Doug Rohrer

Authors

Doug Rohrer

Reviewers

David Capwell, Marcus Eriksson

• Created: 07/Jan/20 17:20
• Updated: 27/Aug/20 15:07
• Resolved: 29/Jan/20 18:21

Description

In some circumstances, we may want to use a non-hard-coded directory as the source for dtest jars. We should allow for a system property to change the default `build` directory.

Issue Links

• links to: GitHub Pull Request #418