Release 3.1.4 about ch.vorburger.exec

[vorburger]

https://maven.apache.org/guides/mini/guide-encryption.html explains what this ^^^ problem was about.

It happened because password happens to have contained ...{...}....

I could change it, but using mvn --encrypt-password is actually a good idea.

With that configured comme il faut:

    [INFO]  * Remote staging into staging profile ID "12bb4759cb85ae"
    [INFO]  * Created staging repository with ID "chvorburger-1051".
    [INFO]  * Staging repository at https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1051

As usual, it wil take a moment for the release to replicate on mirrors.

I'll close this issue when I have manage to use this in a MariaDB4j PR.

[vorburger]

The last release 3.1.3 was on over 1 year ago on 2021-12-03.

And I have since lost my settings.xml ... 🤣 to be able to deploy.

How did this all work again? What user, what credz?

PS BTW this also blocks https://github.com/vorburger/MariaDB4j/issues/696...

[vorburger]

https://central.sonatype.org/publish/publish-maven/ reminded me how to use ~/.m2/settings.xml :

<settings>
  <servers>
    <server>
      <id>ossrh</id>
      <username>vorburger</username>
      <password>PASS</password>
    </server>
  </servers>
</settings>

but then I ran into [ERROR] Failed to execute goal org.sonatype.plugins:nexus-staging-maven-plugin:1.6.13:deploy (injected-nexus-deploy) on project exec: Execution injected-nexus-deploy of goal org.sonatype.plugins:nexus-staging-maven-plugin:1.6.13:deploy failed: Cannot decipher credentials to be used with Nexus!: org.sonatype.plexus.components.sec.dispatcher.shaded.SecDispatcherException: java.io.FileNotFoundException: /home/vorburger/.m2/settings-security.xml (No such file or directory) -> [Help 1]

I'll deal with this another time...

[vorburger]

MariaDB4j/MariaDB4j#718, somewhat to my surprise (it used to take longer?), actually passed!