Google Git
Sign in
apache / cassandra-in-jvm-dtest-api / 7ddfe52d51639817c6c5be86c0c8e317e33620eb
commit7ddfe52d51639817c6c5be86c0c8e317e33620eb[log] [tgz]
authorJon Meredith <jmeredithco@gmail.com>Fri Apr 10 12:04:40 2020 -0600
committerAlex Petrov <oleksandr.petrov@gmail.com>Thu Apr 16 13:14:25 2020 +0200
treebbf8c0a9176338e3a2fc3a562acdc725160a3853
parentd59833f2223a85a4dc3f4ea597384588d5d008df [diff]
Support for replacing logback with alternate logger config (like log4j2)

Not all forks use logback, and there is an (prematurely) closed ticket
indicating that it would be valuable CASSANDRA-13212.

Also had to add 'org.w3c.dom' to the InstanceClassLoader so that
log4j2 could load it's configuration.

Patch by Jon Meredith; reviewed by David Capwell and Alex Petrov for CASSANDRA-15714.
2 files changed
tree: bbf8c0a9176338e3a2fc3a562acdc725160a3853
  1. src/
  2. test/
  3. .gitignore
  4. LICENSE.txt
  5. NOTICE.txt
  6. pom.xml
  7. README.md
README.md

Apache Cassandra in-JVM DTest API

Shared API package for in-JVM distributed tests.

Publishing snapshot

mvn versions:set -DnewVersion=0.0.2-`git rev-parse --short HEAD`-SNAPSHOT
mvn deploy

Releasing

  1. Prepare the release:
mvn release:clean
mvn release:prepare
mvn release:perform

  1. Close staging repository: https://repository.apache.org/#stagingRepositories

  2. Issue a vote on developers mailing list. Add your GPG key signature, release SHA, and staged artifacts to release information.

Additional resources:

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/

GPG Key

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>
  • added to KEYS file
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