After fighting with different plugins for automatically deploy new versions to Maven central we currently use a manual process. As primitive as it is it actually works.
First we generate all thejars we need to generate:
For each module we sign the pom and all the jars:
gpg -ab java-symbol-solver-model/pom.xml gpg -ab java-symbol-solver-model/target/java-symbol-solver-model-0.2.jar gpg -ab java-symbol-solver-model/target/java-symbol-solver-model-0.2-javadoc.jar gpg -ab java-symbol-solver-model/target/java-symbol-solver-model-0.2-sources.jar
We then package everything in a bundle:
mkdir build cd build cp ../java-symbol-solver-model/pom.xml . cp ../java-symbol-solver-model/pom.xml.asc . cp ../java-symbol-solver-model/target/*.jar . cp ../java-symbol-solver-model/target/*.asc . jar -cvf bundle-java-symbol-solver-model.jar pom.xml pom.xml.asc java-symbol-solver-model-0.2.jar java-symbol-solver-model-0.2.jar.asc java-symbol-solver-model-0.2-javadoc.jar java-symbol-solver-model-0.2-javadoc.jar.asc java-symbol-solver-model-0.2-sources.jar java-symbol-solver-model-0.2-sources.jar.asc
Then we sign the parent pom.xml and we zip the parent.pom together with its signature:
gpg -ab pom.xml jar -cvf bundle-java-symbol-solver-parent.jar pom.xml pom.xml.asc
We upload all the bundle jars to sonatype and then release them.