Release 3.1.0

[vorburger]

No description provided.

[vorburger]

Release Notes WIP on main...vorburger:MariaDB4j:CHANGELOG-3.1.0 ...

[vorburger]

The MariaDB4j v3.1.0 will bump (upgrade) its ch.vorburger.exec:exec dependency from 3.1.5 to 3.2.0, see vorburger/ch.vorburger.exec#187, and note vorburger/ch.vorburger.exec@exec-3.1.5...exec-3.2.0. I'm currently waiting for that to "propagate" through Maven Central in order to proceed here.

[vorburger]

./mvnw release:prepare fails due to:

[INFO] 11/17 prepare:scm-commit-release
[INFO] Checking in modified POMs...
[INFO] Executing: /bin/sh -c cd '/home/vorburger/git/github.com/vorburger/MariaDB4j' && 'git' 'add' '--' 'pom.xml' 'mariaDB4j-core/pom.xml' 'mariaDB4j/pom.xml' 'mariaDB4j-springboot/pom.xml' 'mariaDB4j-app/pom.xml' 'mariaDB4j-maven-plugin/pom.xml'
[INFO] Working directory: /home/vorburger/git/github.com/vorburger/MariaDB4j
[INFO] Executing: /bin/sh -c cd '/home/vorburger/git/github.com/vorburger/MariaDB4j' && 'git' 'rev-parse' '--show-prefix'
[INFO] Working directory: /home/vorburger/git/github.com/vorburger/MariaDB4j
[INFO] Executing: /bin/sh -c cd '/home/vorburger/git/github.com/vorburger/MariaDB4j' && 'git' 'status' '--porcelain' '.'
[INFO] Working directory: /home/vorburger/git/github.com/vorburger/MariaDB4j
[INFO] 12/17 prepare:scm-tag
[INFO] Tagging release with the label mariaDB4j-3.0.2...
[INFO] Executing: /bin/sh -c cd '/home/vorburger/git/github.com/vorburger/MariaDB4j' && 'git' 'tag' '-F' '/tmp/maven-scm-676608308.commit' 'mariaDB4j-3.0.2'
[INFO] Working directory: /home/vorburger/git/github.com/vorburger/MariaDB4j
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for mariaDB4j-pom 3.1.0-SNAPSHOT:
[INFO]
[INFO] mariaDB4j-pom ...................................... FAILURE [01:18 min]
[INFO] mariaDB4j-core ..................................... SKIPPED
[INFO] mariaDB4j (all-in-one artifact) .................... SKIPPED
[INFO] mariaDB4j-springboot ............................... SKIPPED
[INFO] mariaDB4j-app ...................................... SKIPPED
[INFO] mariaDB4j-maven-plugin ............................. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  01:19 min
[INFO] Finished at: 2024-03-27T23:25:03+01:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:3.0.1:prepare (default-cli) on project mariaDB4j-pom: Unable to tag SCM
[ERROR] Provider message:
[ERROR] The git-tag command failed.
[ERROR] Command output:
[ERROR] fatal: tag 'mariaDB4j-3.0.2' already exists

which is correct... except why is trying to tag 3.0.2 when I'm trying to release 3.1.0 ?!

[vorburger]

I've just successfully deployed a MariaDB4j 3.1.0 release to Maven Central. (It may take a few hours to "propagate".)

For the record, the tag was a bit of a mess; locally originally 9e27d2a, but remote via #921 (because cannot push with PR) 55d679c.

The Release Notes for MariaDB4j v3.1.0 are here and here.

If you use MariaDB4j professionally, please consider to, either:

• Taking a Tidelift subscription, or
• GitHub Sponsor me,

to support future maintenance!