To avoid conflicts with the version of Guava used by Drill and versions used by other dependencies, Guava was shaded.
guava.version
property and to the version of the artifact in drill-shaded/drill-shaded-guava/pom.xml
file.shaded.guava.version
property in the root pom.xml
file.drill-shaded-guava
module.Only PMC members have an access for pushing artifacts to the Apache repository.
Setup your development env according to this instruction.
Set passphrase variable without putting it into shell history:
read -s GPG_PASSPHRASE
Change directory to drill/drill-shaded/drill-shaded-guava
.
maven-gpg-plugin
plugin wasn’t added to the pom.xml
, runmvn clean verify gpg:sign install:install deploy:deploy -Darguments="-Dgpg.passphrase=${GPG_PASSPHRASE} -Dgpg.keyname=${GPG_KEY_ID}"
maven-gpg-plugin
plugin, runmvn deploy -Darguments="-Dgpg.passphrase=${GPG_PASSPHRASE} -Dgpg.keyname=${GPG_KEY_ID}"
jar
and pom
files are uploadedjar
and pom
file has a corresponding signature file (*.asc)If something went wrong, press Drop
to remove the staging repository.
Select uploaded staging repository and press Close
button.
Verify that all checks are passed and staging repository was closed. Otherwise, drop staging repository and fix errors.
Select uploaded staging repository and press Release
button.
Find deployed artifacts at repository.apache.org
Artifacts will become available within 24 hours.