Testing GH actions with a snapshot version

Author: jcpitre

.github/workflows/publish_assets.yml

@@ -99,7 +99,7 @@ jobs:
           VARIABLES_TO_EXTRACT: 'MAVEN_GPG_PASSPHRASE, MAVEN_GPG_PRIVATE_KEY, MAVEN_CENTRAL_PORTAL_TOKEN_USERNAME, MAVEN_CENTRAL_PORTAL_TOKEN_PASSWORD'
           ONE_PASSWORD_SECRET_REFERENCES: ${{ vars.ONE_PASSWORD_SECRET_REFERENCES }}
 
-      - name: Build and Publish to Sonatype
+      - name: Build and Publish to Maven Central
         run: |
           # Publishing to Maven Central will fail if the version is a snapshot, i.e. there is no version tag
           # directly on the current commit.

build.gradle

@@ -15,12 +15,15 @@
  */
 /*
  * A note about publishing and signing.
- * Maven central requires that artifacts be signed. And upload is done to Sonatype.
+ * Maven central requires that artifacts be signed. And upload is done via Maven Central Portal.
  * To publish you will need these environment variables defined:
+ *       MAVEN_CENTRAL_PORTAL_TOKEN_USERNAME
+ *       MAVEN_CENTRAL_PORTAL_TOKEN_PASSWORD
  *       MAVEN_GPG_PRIVATE_KEY
  *       MAVEN_GPG_PASSPHRASE
- * Suggestion is to put these in a shell script with restricted read permissions, then source it before calling
- * ./gradlew publish.
+ * If run manually, the suggestion is to put these in a shell script with restricted read permissions,
+ * then source it before calling ./gradlew
+ * If run from a Github action, make sure these environment variables are defined.
  */
 plugins {
     id 'java'
@@ -38,7 +41,7 @@ allprojects {
 
     // Per the axion-release plugin, this computes the project version based
     // on the most recent tag in the repo.
-    version "1.2"
+    version scmVersion.version
 
     repositories {
         mavenCentral()

scripts/publish_to_maven_central.sh

@@ -22,7 +22,7 @@ bearer_token=$(echo "$MAVEN_CENTRAL_PORTAL_TOKEN_USERNAME:$MAVEN_CENTRAL_PORTAL_
 # publishingType=USER_MANAGED means that the artefacts will be uploaded and verified, but not yet published.
 # See https://central.sonatype.com/publishing/deployments (you need to login as mobilitydata)
 # From this page you can examine the list of artefacts, and either drop them or release them.
-# If you want to remove that step, use publishingType=AUTOMATIC, that will publish directly.
+# If you want to remove that step, use publishingType=AUTOMATIC below, that will publish directly.
 # Note that once published you cannot remove or alter the artifacts.
 answer=$(curl --request POST \
   --verbose \