chore: #196 Allow to bypass Maven central deploy

Signed-off-by: Laurent Broudoux <[email protected]>

Author: lbroudoux

.github/workflows/release.yml

@@ -11,6 +11,11 @@ on:
       nextVersion:
         description: 'Next version after release (-SNAPSHOT will be added automatically)'
         required: true
+      deployActive:
+        description: 'Deploy Active value for JReleaser'
+        required: false
+        default: 'ALWAYS'
+        type: string
 jobs:
   release:
     name: Release
@@ -58,6 +63,7 @@ jobs:
           JRELEASER_GPG_SECRET_KEY: ${{ secrets.JRELEASER_GPG_SECRET_KEY }}
           JRELEASER_GPG_PUBLIC_KEY: ${{ secrets.JRELEASER_GPG_PUBLIC_KEY }}
           JRELEASER_GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          JRELEASER_DEPLOY_ACTIVE: ${{ github.event.inputs.deployActive }}
         run: mvn -N -Prelease jreleaser:assemble jreleaser:full-release
 
       # Persist logs

jreleaser.yml

@@ -3,8 +3,9 @@ project:
   description: Microcks Testcontainers Java library
   longDescription: Microcks Testcontainers Java library
   copyright: The Microcks Authors
-  java:
-    version: 8
+  languages:
+    java:
+      version: '8'
 
 signing:
   active: ALWAYS
@@ -42,6 +43,7 @@ deploy:
         applyMavenCentralRules: true
         stagingRepositories:
           - target/staging-deploy
+        verifyUrl: 'https://repo1.maven.org/maven2/{{path}}/{{filename}}'
     pomchecker:
       failOnWarning: false
       failOnError: false