Update to new maven deployment

documentation/releasing.md

@@ -41,14 +41,6 @@ Items on Release day:
     - `LSP4J_BUILD_NUMBER` -> the build that was just run above
     - `DRY_RUN` -> `false`
 - [ ] Add to the deploy job description `v1.0.0`
-- [ ] Promote the staged repository to maven central
-    - [Login to Nexus](https://oss.sonatype.org/#stagingRepositories)
-        - To obtain permission add request to [OSSRH-26079](https://issues.sonatype.org/browse/OSSRH-26079)
-    - go to *Staging Repositories*, after a short delay the staged LSP4J release should appear (you may need to press *Refresh*)
-    - click the staged LSP4J repo
-    - press the *Close* button located in the toolbar. This runs activities, including checking various rules
-    - once the rules are done (if successful), press the *Release* button (you may need to press *Refresh* to enable the *Release* button)
-    - check https://search.maven.org/search?q=g:org.eclipse.lsp4j to make sure the latest release has arrived - this takes a while, 15 minutes for the files to be [on the server](https://repo1.maven.org/maven2/org/eclipse/lsp4j/) and even longer for the [search indexes](https://search.maven.org/search?q=g:org.eclipse.lsp4j) to update
 - [ ] Update the meta-data on [PMI downloads page](https://projects.eclipse.org/projects/technology.lsp4j/downloads)
 - [ ] Tag the release. Example: `git tag -a v1.0.0 HEAD -m"LSP4J 1.0.0" && git push origin v1.0.0`
 - [ ] Contribute to Simrel. See [Simrel contribution example](https://git.eclipse.org/r/#/c/158624/)

releng/release-eclipse.sh

@@ -44,21 +44,23 @@ unzip -q maven-repository.zip
 find maven-repository -name '*.pom' | while read i
 do
     base="${i%.*}"
-    # The centos-7 agent is used because it provides gpg 2.0.x
-    # and we sign for OSSRH with gpg maven plug-in run at the command
-    # line.
-    # If a newer GPG version (> 2.1+) is used,
-    # --pinentry-mode loopback needs to be added as gpg argument in the pom.xml.
-    # If centos changes we may need to add the gpg arguments to some pom.xml
-    # somewhere
-    $ECHO mvn \
-        gpg:sign-and-deploy-file \
+    $ECHO mvn -f gpgparameters.pom \
+        org.apache.maven.plugins:maven-gpg-plugin:3.2.8:sign \
+        -DpomFile=${base}.pom \
+        -Dfile=${base}.jar \
+        -Dsources=${base}-sources.jar \
+        -Djavadoc=${base}-javadoc.jar
+    $ECHO mvn -f gpgparameters.pom \
+        deploy:deploy-file \
         -DpomFile=${base}.pom \
         -Dfile=${base}.jar \
         -Dsources=${base}-sources.jar \
         -Djavadoc=${base}-javadoc.jar \
-        -Durl=https://oss.sonatype.org/service/local/staging/deploy/maven2 \
-        -DrepositoryId=ossrh
+        -Dfiles=${base}.jar.asc,${base}-sources.jar.asc,${base}-javadoc.jar.asc \
+        -Dclassifiers=,sources,javadoc \
+        -Dtypes=jar,jar,jar \
+        -DrepositoryId=central \
+        -Durl=https://central.sonatype.com/repository/maven-releases
 done
 
 if [ "$DRY_RUN" == "false" ]; then