Release 2.0.0.Alpha1

[ppalaga]

The release workflow cannot upload the artifacts to s01.oss.sontatype.org:

[INFO] [INFO] --- maven-deploy-plugin:2.8.2:deploy (default-deploy) @ quarkus-xmlsec-parent ---
[INFO] [INFO] Uploading to oss.sonatype: https://s01.oss.sonatype.org/service/local/staging/deploy/maven2/io/quarkiverse/xmlsec/quarkus-xmlsec-parent/2.0.0.Alpha1/quarkus-xmlsec-parent-2.0.0.Alpha1.pom
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [INFO] Reactor Summary for Quarkus - XMLSec - Parent 2.0.0.Alpha1:
[INFO] [INFO] 
[INFO] [INFO] Quarkus - XMLSec - Parent .......................... FAILURE [  3.207 s]
[INFO] [INFO] Quarkus - XMLSec - BOM ............................. SKIPPED
[INFO] [INFO] Quarkus - XMLSec ................................... SKIPPED
[INFO] [INFO] Quarkus - XMLSec - Deployment ...................... SKIPPED
[INFO] [INFO] Quarkus - XMLSec - Integration Tests ............... SKIPPED
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [INFO] BUILD FAILURE
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [INFO] Total time:  3.491 s
[INFO] [INFO] Finished at: 2023-02-08T09:10:10Z
[INFO] [INFO] ------------------------------------------------------------------------
Error: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project quarkus-xmlsec-parent: Failed to deploy artifacts: Could not transfer artifact io.quarkiverse.xmlsec:quarkus-xmlsec-parent:pom:2.0.0.Alpha1 from/to oss.sonatype (https://s01.oss.sonatype.org/service/local/staging/deploy/maven2/): authentication failed for https://s01.oss.sonatype.org/service/local/staging/deploy/maven2/io/quarkiverse/xmlsec/quarkus-xmlsec-parent/2.0.0.Alpha1/quarkus-xmlsec-parent-2.0.0.Alpha1.pom, status: 401 Unauthorized -> [Help 1]

[ppalaga]

Any idea why this happens @gastaldi ?

Maybe the secrets need to be set differently, now that I started relying on settings.xml set up by actions/setup-java@v3?

[gastaldi]

@ppalaga that's weird, maybe because ./mvnw is being used instead? I've updated the scripts in #86 to the latest actions and settings. Hopefully that should work

[gastaldi]

Fixed in https://github.com/quarkiverse/quarkus-xmlsec/actions/runs/4124668633/jobs/7124203659

[ppalaga]

@gastaldi thanks, it worked. I dared to move the attributes.adoc to a separate commit before the release, so that we do not need to do the manual tag juggling: https://github.com/quarkiverse/quarkus-xmlsec/blob/main/.github/workflows/release.yml#L55-L61

[gastaldi]

Ahhh fantastic!! Can you provide a PR updating the official template in https://github.com/quarkusio/quarkus/blob/main/independent-projects/tools/base-codestarts/src/main/resources/codestarts/quarkus-extension/code/quarkiverse/java/.github/workflows/release.yml ?

[ppalaga]

Here is the PR: quarkusio/quarkus#31046

[gsmet]

I might miss something but how is the version in the attributes updated given the version will be set later by release:prepare?

[gastaldi]

@gsmet The version is taken from the project.yml, not the pom.xml

[ppalaga]

Yes, there is a plugin in doc module reading project.yaml and setting Maven properties out of it that are then used by the resources filtering.