commit | 1e3bc4c3b34eae563547899645bfb3f0a1948c79 | [log] [tgz] |
---|---|---|
author | Doug Rohrer <doug@therohrers.org> | Thu May 18 20:44:43 2023 -0400 |
committer | Dinesh Joshi <djoshi@apache.org> | Thu May 18 23:01:10 2023 -0700 |
tree | 539500260911f9f8ffffa3832149ebebe6ebb684 | |
parent | 07cb6fea534a65152862cabc36e260c6d3776f36 [diff] |
Add JMX utility class to in-jvm dtest to ease development of new tests using JMX While reviewing CASSANDRA-18511, some repetitive code was identified across the 4 branches, and 2 different tests, that would also be repeated for any new usages of the JMX support in the in-jvm dtest framework. Therefore, a utility class should be added to the dtest-api's `shared` package that will simplify some of this repetitive and error-prone code. patch by Doug Rohrer; reviewed by Jon Meredith, Dinesh Joshi for CASSANDRA-18537
Shared API package for in-JVM distributed tests.
mvn versions:set -DnewVersion=`xpath -n -q -e '/project/version/text()' pom.xml | awk -F- '{print $1}'`-`git rev-parse --short HEAD`-SNAPSHOT mvn deploy
mvn release:clean CURRENT=0.0.CURRENT NEXT_DEV=0.0.NEXT mvn -DreleaseVersion=$CURRENT -Dtag=$CURRENT -DdevelopmentVersion=$NEXT_DEV-SNAPSHOT release:prepare mvn release:perform
Close staging repository: https://repository.apache.org/#stagingRepositories
Issue a vote on developers mailing list. Add your GPG key signature, release SHA, and staged artifacts to release information.
Parent pom location: https://maven.apache.org/pom/asf/ Maven distribution docs: http://www.apache.org/dev/publishing-maven-artifacts.html Creating a new reposotory: https://selfserve.apache.org/
To generate key, run:
gpg --full-gen-key
To be able to sign releases with this key, make sure your key is:
gpg --list-sigs "<YOUR_NAME>" gpg --verbose --send-keys --keyserver hkps://hkps.pool.sks-keyservers.net <YOUR_KEY_IDENTIFIER_HERE> # to test if it has worked: gpg --verbose --recv-keys --keyserver hkps://hkps.pool.sks-keyservers.net <YOUR_KEY_IDENTIFIER_HERE>
svn co --depth files https://dist.apache.org/repos/dist/release/cassandra/ release (gpg --list-sigs "<YOUR_NAME>" && gpg --armor --export "<YOUR_NAME>") >> KEYS svn commit KEYS -m "Add <YOUR NAME>'s key for releases" # or ask some PMC to do this for you by opening CASSANDRA jira, like this one: https://issues.apache.org/jira/browse/CASSANDRA-15534