Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Initial addition of 10.11.5 with working unit tests. #771

Closed
wants to merge 4 commits into from

Conversation

TheKnowles
Copy link
Contributor

mysql binaries are modified in code.
win32 has been replaced with winx64 from maria downloads.
Security unit test has been updated to account for root user changes in 10.4.

@TheKnowles
Copy link
Contributor Author

This is a smaller, targeted pass of #710 off of main for Java 17 / Spring Boot 3.

10.11.5 is the latest long term supported release from maria.

Related: #344 #699

Copy link
Contributor Author

@TheKnowles TheKnowles left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've left comments on the pain points from the previous PR.

executables.putIfAbsent(Server, () -> new File(baseDir, "bin/mysqld" + getExtension()));
executables.putIfAbsent(Client, () -> new File(baseDir, "bin/mysql" + getExtension()));
executables.putIfAbsent(Dump, () -> new File(baseDir, "bin/mysqldump" + getExtension()));
executables.putIfAbsent(Server, () -> new File(baseDir, "bin/mariadbd" + getExtension()));
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we kept the original mysql names, we would have to modify the installation script and that becomes very brittle very quickly.

executables.putIfAbsent(PrintDefaults, () -> new File(baseDir, "bin/my_print_defaults" + getExtension()));
executables.putIfAbsent(InstallDB, () -> {
File bin = new File(baseDir, "bin/mysql_install_db" + getExtension());
File bin = new File(baseDir, "bin/mariadb-install-db" + getExtension());
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Even if we copied over the new script name into the old script name, it will reference the new binaries. Because these were not chmod +x it would fail because it could not find that executable.

Updating the new script with the old names was untenable.

</dependency>
<dependency>
<groupId>ch.vorburger.mariaDB4j</groupId>
<artifactId>mariaDB4j-db-mac64</artifactId>
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Per our previous conversation on the last PR, maxOS support has been dropped. I am experimenting with some virtualbox vms to avoid buying a mac machine. But for now, mac is bespoke and not easily fixed on a linux machine.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I'm fine with this; given even this old Mac x86 10.2.11 increasingly doesn't work for new Mac users on M1/M2/M3 ARM CPUs anymore anyway, see #497 and https://github.com/MariaDB4j/MariaDB4j#how-using-existing-native-mariadb-binaries. The real solution is probably #296 anyway... maybe I'll play with that one of these days!

mysql binaries are modified in code.
win32 has been replaced with winx64 from maria downloads.
Security unit test has been updated to account for root user changes in 10.4.
@TheKnowles TheKnowles force-pushed the binary-10-11-5-update branch from 83db6f4 to 902fda9 Compare September 15, 2023 20:54
@vorburger
Copy link
Collaborator

@TheKnowles Great to hear back from you - Thank You for re-engaging, after #710.

I will try to have a closer look at this later today or tomorrow!

@vorburger
Copy link
Collaborator

@TheKnowles OK, right, now I better understand... so those would break using MariaDB4j with older MariaDB where binaries still used to be named mysqld instead of mariadbd, right? I'm personally not really fundamentally opposed to this (anymore), but I do wonder what impact this would have on the (many) other users of this project...

It IS a "breaking" change (for MariaDB4j). At the very least, this probably justifies changing the version from 3.0.x to 3.1.x... (@TheKnowles not asking for you to do that in this PR; I would do it.)

Does anyone watch this repo and is reading along here and would have any opinion about this? Does e.g. anyone still use a current MariaDB4j v3.0.1 release but overrides the POM dependency to an OLDER MariaDB than the 10.2.11 which MariaDB4j v3.0.1 comes with? Or use a custom binary artefact built in-house? Or does everyone "just want it to work out of the box" and is fine with, even very happy about and glad for, a future new MariaDB4j release to just depend on latest MariaDB 10.11.5 and not bothered by not able to override the binaries to older versions? Then I'm happy to merge this...

@mosesn @mrdziuban do you have any views pro/con about this PR? Happy to see it? Breaking anything for you internally?

Copy link
Collaborator

@vorburger vorburger left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm OK to merge this as-is.

I just need to separately push the binaries to Maven central, then this will build, and I'll merge it.

@vorburger
Copy link
Collaborator

It IS a "breaking" change (for MariaDB4j). At the very least, this probably justifies changing the version from 3.0.x to 3.1.x... (@TheKnowles not asking for you to do that in this PR; I would do it.)

I think this makes sense, so what I'll do is release a 3.0.2 (without this), then bump to 3.1.0-SNAPSHOT and merge this (I'll hold releasing it, for now).

I just need to separately push the binaries to Maven central, then this will build

Done, and it's green on Linux, but CI fails on Windows... I don't have a Windows machine. @TheKnowles have you tested this locally on Windows? Do you want to have a closer look and see what that ERROR: Can't write to mysqld's stdin CI failure on Windows is about? @mosesn do you or your colleagues use Windows and want to contribute to debug this?

@vorburger
Copy link
Collaborator

but CI fails on Windows... I

The reason seems to be this:

[main] INFO ch.vorburger.mariadb4j.Util - Unpacked 73 files from classpath*:ch/vorburger/mariadb4j/mariadb-10.11.5/winx64/** to C:\Users\RUNNER~1\AppData\Local\Temp\MariaDB4j\base
[main] INFO ch.vorburger.mariadb4j.DB - Installing a new embedded database to: C:\Users\RUNNER~1\AppData\Local\Temp\MariaDB4j\base
[main] INFO ch.vorburger.exec.ManagedProcess - Starting Program [C:\Users\RUNNER~1\AppData\Local\Temp\MariaDB4j\base\bin\mariadb-install-db.exe, --datadir=C:\Users\runneradmin\AppData\Local\Temp\MariaDB4j\data\54232] (in working directory C:\Users\RUNNER~1\AppData\Local\Temp\MariaDB4j\base)
[main] INFO ch.vorburger.exec.ManagedProcess - Thread is now going to wait for this process to terminate itself: Program [C:\Users\RUNNER~1\AppData\Local\Temp\MariaDB4j\base\bin\mariadb-install-db.exe, --datadir=C:\Users\runneradmin\AppData\Local\Temp\MariaDB4j\data\54232] (in working directory C:\Users\RUNNER~1\AppData\Local\Temp\MariaDB4j\base)
[Exec Stream Pumper] INFO ch.vorburger.exec.ManagedProcess - mariadb-install-db.exe: Running bootstrap
[Exec Stream Pumper] INFO ch.vorburger.exec.ManagedProcess - mariadb-install-db.exe: '"C:\Users\RUNNER~1\AppData\Local\Temp\MariaDB4j\base\bin\mysqld.exe"' is not recognized as an internal or external command,
[Exec Stream Pumper] INFO ch.vorburger.exec.ManagedProcess - mariadb-install-db.exe: operable program or batch file.
[Exec Stream Pumper] INFO ch.vorburger.exec.ManagedProcess - mariadb-install-db.exe: Creating my.ini file
[Exec Stream Pumper] ERROR ch.vorburger.exec.ManagedProcess - mariadb-install-db.exe: FATAL ERROR: database creation failed
[Exec Stream Pumper] INFO ch.vorburger.exec.ManagedProcess - mariadb-install-db.exe: ERROR: Can't write to mysqld's stdin

So for some reason, even though it's mostly changed from mysql* to mariadb something, in the core MariaDB Windows binaries, not this MariaDB4j wrapper project, still calls a mysqld.exe? Or did we package it wrong - something missing/wrong in the mariaDB4j-db-winx64-10.11.5/prepare.xml in this PR? @TheKnowles do you want to further investigate this? Thank You!

@TheKnowles
Copy link
Contributor Author

but CI fails on Windows... I

The reason seems to be this:

[main] INFO ch.vorburger.mariadb4j.Util - Unpacked 73 files from classpath*:ch/vorburger/mariadb4j/mariadb-10.11.5/winx64/** to C:\Users\RUNNER~1\AppData\Local\Temp\MariaDB4j\base
[main] INFO ch.vorburger.mariadb4j.DB - Installing a new embedded database to: C:\Users\RUNNER~1\AppData\Local\Temp\MariaDB4j\base
[main] INFO ch.vorburger.exec.ManagedProcess - Starting Program [C:\Users\RUNNER~1\AppData\Local\Temp\MariaDB4j\base\bin\mariadb-install-db.exe, --datadir=C:\Users\runneradmin\AppData\Local\Temp\MariaDB4j\data\54232] (in working directory C:\Users\RUNNER~1\AppData\Local\Temp\MariaDB4j\base)
[main] INFO ch.vorburger.exec.ManagedProcess - Thread is now going to wait for this process to terminate itself: Program [C:\Users\RUNNER~1\AppData\Local\Temp\MariaDB4j\base\bin\mariadb-install-db.exe, --datadir=C:\Users\runneradmin\AppData\Local\Temp\MariaDB4j\data\54232] (in working directory C:\Users\RUNNER~1\AppData\Local\Temp\MariaDB4j\base)
[Exec Stream Pumper] INFO ch.vorburger.exec.ManagedProcess - mariadb-install-db.exe: Running bootstrap
[Exec Stream Pumper] INFO ch.vorburger.exec.ManagedProcess - mariadb-install-db.exe: '"C:\Users\RUNNER~1\AppData\Local\Temp\MariaDB4j\base\bin\mysqld.exe"' is not recognized as an internal or external command,
[Exec Stream Pumper] INFO ch.vorburger.exec.ManagedProcess - mariadb-install-db.exe: operable program or batch file.
[Exec Stream Pumper] INFO ch.vorburger.exec.ManagedProcess - mariadb-install-db.exe: Creating my.ini file
[Exec Stream Pumper] ERROR ch.vorburger.exec.ManagedProcess - mariadb-install-db.exe: FATAL ERROR: database creation failed
[Exec Stream Pumper] INFO ch.vorburger.exec.ManagedProcess - mariadb-install-db.exe: ERROR: Can't write to mysqld's stdin

So for some reason, even though it's mostly changed from mysql* to mariadb something, in the core MariaDB Windows binaries, not this MariaDB4j wrapper project, still calls a mysqld.exe? Or did we package it wrong - something missing/wrong in the mariaDB4j-db-winx64-10.11.5/prepare.xml in this PR? @TheKnowles do you want to further investigate this? Thank You!

Yes I will investigate. I only ran the simulated winx64 start.

@TheKnowles
Copy link
Contributor Author

TheKnowles commented Sep 17, 2023

but CI fails on Windows... I

The reason seems to be this:

[main] INFO ch.vorburger.mariadb4j.Util - Unpacked 73 files from classpath*:ch/vorburger/mariadb4j/mariadb-10.11.5/winx64/** to C:\Users\RUNNER~1\AppData\Local\Temp\MariaDB4j\base
[main] INFO ch.vorburger.mariadb4j.DB - Installing a new embedded database to: C:\Users\RUNNER~1\AppData\Local\Temp\MariaDB4j\base
[main] INFO ch.vorburger.exec.ManagedProcess - Starting Program [C:\Users\RUNNER~1\AppData\Local\Temp\MariaDB4j\base\bin\mariadb-install-db.exe, --datadir=C:\Users\runneradmin\AppData\Local\Temp\MariaDB4j\data\54232] (in working directory C:\Users\RUNNER~1\AppData\Local\Temp\MariaDB4j\base)
[main] INFO ch.vorburger.exec.ManagedProcess - Thread is now going to wait for this process to terminate itself: Program [C:\Users\RUNNER~1\AppData\Local\Temp\MariaDB4j\base\bin\mariadb-install-db.exe, --datadir=C:\Users\runneradmin\AppData\Local\Temp\MariaDB4j\data\54232] (in working directory C:\Users\RUNNER~1\AppData\Local\Temp\MariaDB4j\base)
[Exec Stream Pumper] INFO ch.vorburger.exec.ManagedProcess - mariadb-install-db.exe: Running bootstrap
[Exec Stream Pumper] INFO ch.vorburger.exec.ManagedProcess - mariadb-install-db.exe: '"C:\Users\RUNNER~1\AppData\Local\Temp\MariaDB4j\base\bin\mysqld.exe"' is not recognized as an internal or external command,
[Exec Stream Pumper] INFO ch.vorburger.exec.ManagedProcess - mariadb-install-db.exe: operable program or batch file.
[Exec Stream Pumper] INFO ch.vorburger.exec.ManagedProcess - mariadb-install-db.exe: Creating my.ini file
[Exec Stream Pumper] ERROR ch.vorburger.exec.ManagedProcess - mariadb-install-db.exe: FATAL ERROR: database creation failed
[Exec Stream Pumper] INFO ch.vorburger.exec.ManagedProcess - mariadb-install-db.exe: ERROR: Can't write to mysqld's stdin

So for some reason, even though it's mostly changed from mysql* to mariadb something, in the core MariaDB Windows binaries, not this MariaDB4j wrapper project, still calls a mysqld.exe? Or did we package it wrong - something missing/wrong in the mariaDB4j-db-winx64-10.11.5/prepare.xml in this PR? @TheKnowles do you want to further investigate this? Thank You!

Yes I will investigate. I only ran the simulated winx64 start.

@vorburger Ok, this should be good to go.

There were a handful of issues:

  1. We needed to add the mysqld binaries in prepare.xml for Windows. They got called as you previously found.
  2. Once those were added, we also needed server.dll and server.lib
  3. Windows does not implement the auth introduced in 10.4 where the root user no longer has an empty password. So we'll do a check in the unit test to just use the root user instead of the current user.

I have built and run all unit tests passing on Windows 11.

@vorburger
Copy link
Collaborator

Cool, Thank You so much!

I'll re-test this as soon as I can get to it.

vorburger pushed a commit that referenced this pull request Sep 18, 2023
@vorburger
Copy link
Collaborator

Because I already released https://repo.maven.apache.org/maven2/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5/ (NB the artifactId is now new mariaDB4j-db-winx64, VS previous mariaDB4j-db-win32) on the day before yesterday to Maven Central, while first testing this, but then the scripts here got changed, I wil now have to re-release it; I'll use 10.11.5.1 for that (even though there is of course no such MariaDB binary version).

This time, I'll temporarily "hack" things, and not actually deploy it just yet, but instead mvn install (not deploy) the artifact on CI, in a commit which I will drop again before ultimately merging this, to test that this really work. I will be doing this in #772, under which this will get merged (once it works).

vorburger added a commit that referenced this pull request Sep 18, 2023
includes bumping MariaDB v10.11.5 Windows binary to 10.11.5.1;
see #771 (comment).
vorburger added a commit that referenced this pull request Sep 18, 2023
includes bumping MariaDB v10.11.5 Windows binary to 10.11.5.1;
see #771 (comment).
@vorburger
Copy link
Collaborator

bump to 3.1.0-SNAPSHOT

done in #779 (@TheKnowles please ignore the merge conflicts that caused here; I will merge the commits from your PR here under the overall PR #772).

This time, I'll temporarily "hack" things, and not actually deploy it just yet, but instead mvn install (not deploy) the artifact on CI, in a commit which I will drop again before ultimately merging this, to test that this really work. I

see c6814e6

vorburger pushed a commit that referenced this pull request Sep 18, 2023
vorburger added a commit that referenced this pull request Sep 18, 2023
includes bumping MariaDB v10.11.5 Windows binary to 10.11.5.1;
see #771 (comment).
vorburger pushed a commit that referenced this pull request Sep 18, 2023
vorburger added a commit that referenced this pull request Sep 18, 2023
includes bumping MariaDB v10.11.5 Windows binary to 10.11.5.1;
see #771 (comment).
@vorburger
Copy link
Collaborator

vorburger commented Sep 18, 2023

Because I already released https://repo.maven.apache.org/maven2/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5/ (NB the artifactId is now new mariaDB4j-db-winx64, VS previous mariaDB4j-db-win32) on the day before yesterday to Maven Central, while first testing this, but then the scripts here got changed, I wil now have to re-release it; I'll use 10.11.5.1 for that (even though there is of course no such MariaDB binary version).

This does not work... 😭 The nexus-staging Maven plugin appears to want to deploy a 10.11.5.1 as both that as well as a 10.11.5, and (obviously) fails when doing the latter, which aborts the entire deploy, check this out:

[INFO] --- install:3.1.0:install (default-install) @ mariaDB4j-db-winx64 ---
[INFO] Installing /home/vorburger/git/github.com/vorburger/MariaDB4j/DBs/mariaDB4j-db-10.11.5/mariaDB4j-db-winx64-10.11.5/pom.xml to /home/vorburger/.m2/repository/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5.1/mariaDB4j-db-winx64-10.11.5.1.pom
[INFO] Installing /home/vorburger/git/github.com/vorburger/MariaDB4j/DBs/mariaDB4j-db-10.11.5/mariaDB4j-db-winx64-10.11.5/target/mariaDB4j-db-winx64-10.11.5.1.jar to /home/vorburger/.m2/repository/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5.1/mariaDB4j-db-winx64-10.11.5.1.jar
[INFO] Installing /home/vorburger/git/github.com/vorburger/MariaDB4j/DBs/mariaDB4j-db-10.11.5/mariaDB4j-db-winx64-10.11.5/target/mariaDB4j-db-winx64-10.11.5.1-sources.jar to /home/vorburger/.m2/repository/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5.1/mariaDB4j-db-winx64-10.11.5.1-sources.jar
[INFO] Installing /home/vorburger/git/github.com/vorburger/MariaDB4j/DBs/mariaDB4j-db-10.11.5/mariaDB4j-db-winx64-10.11.5/target/mariaDB4j-db-winx64-10.11.5.1.jar.asc to /home/vorburger/.m2/repository/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5.1/mariaDB4j-db-winx64-10.11.5.1.jar.asc
[INFO] Installing /home/vorburger/git/github.com/vorburger/MariaDB4j/DBs/mariaDB4j-db-10.11.5/mariaDB4j-db-winx64-10.11.5/target/mariaDB4j-db-winx64-10.11.5.1.pom.asc to /home/vorburger/.m2/repository/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5.1/mariaDB4j-db-winx64-10.11.5.1.pom.asc
[INFO] Installing /home/vorburger/git/github.com/vorburger/MariaDB4j/DBs/mariaDB4j-db-10.11.5/mariaDB4j-db-winx64-10.11.5/target/mariaDB4j-db-winx64-10.11.5.1-sources.jar.asc to /home/vorburger/.m2/repository/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5.1/mariaDB4j-db-winx64-10.11.5.1-sources.jar.asc
[INFO]
[INFO] --- nexus-staging:1.6.13:deploy (injected-nexus-deploy) @ mariaDB4j-db-winx64 ---
[INFO] Performing local staging (local stagingDirectory="/home/vorburger/git/github.com/vorburger/MariaDB4j/DBs/mariaDB4j-db-10.11.5/mariaDB4j-db-winx64-10.11.5/target/nexus-staging/staging")...
[INFO]  + Using server credentials "ossrh" from Maven settings.
[INFO]  * Connected to Nexus at https://oss.sonatype.org:443/, is version 2.15.1-02 and edition "Professional"
[INFO]  * Using staging profile ID "12bb4759cb85ae" (matched by Nexus).
[INFO] Installing /home/vorburger/git/github.com/vorburger/MariaDB4j/DBs/mariaDB4j-db-10.11.5/mariaDB4j-db-winx64-10.11.5/target/mariaDB4j-db-winx64-10.11.5.1.jar to /home/vorburger/git/github.com/vorburger/MariaDB4j/DBs/mariaDB4j-db-10.11.5/mariaDB4j-db-winx64-10.11.5/target/nexus-staging/staging/12bb4759cb85ae/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5.1/mariaDB4j-db-winx64-10.11.5.1.jar
[INFO] Installing /home/vorburger/git/github.com/vorburger/MariaDB4j/DBs/mariaDB4j-db-10.11.5/mariaDB4j-db-winx64-10.11.5/pom.xml to /home/vorburger/git/github.com/vorburger/MariaDB4j/DBs/mariaDB4j-db-10.11.5/mariaDB4j-db-winx64-10.11.5/target/nexus-staging/staging/12bb4759cb85ae/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5.1/mariaDB4j-db-winx64-10.11.5.1.pom
[INFO] Installing /home/vorburger/git/github.com/vorburger/MariaDB4j/DBs/mariaDB4j-db-10.11.5/mariaDB4j-db-winx64-10.11.5/target/mariaDB4j-db-winx64-10.11.5.1-sources.jar to /home/vorburger/git/github.com/vorburger/MariaDB4j/DBs/mariaDB4j-db-10.11.5/mariaDB4j-db-winx64-10.11.5/target/nexus-staging/staging/12bb4759cb85ae/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5.1/mariaDB4j-db-winx64-10.11.5.1-sources.jar
[INFO] Installing /home/vorburger/git/github.com/vorburger/MariaDB4j/DBs/mariaDB4j-db-10.11.5/mariaDB4j-db-winx64-10.11.5/target/mariaDB4j-db-winx64-10.11.5.1.jar.asc to /home/vorburger/git/github.com/vorburger/MariaDB4j/DBs/mariaDB4j-db-10.11.5/mariaDB4j-db-winx64-10.11.5/target/nexus-staging/staging/12bb4759cb85ae/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5.1/mariaDB4j-db-winx64-10.11.5.1.jar.asc
[INFO] Installing /home/vorburger/git/github.com/vorburger/MariaDB4j/DBs/mariaDB4j-db-10.11.5/mariaDB4j-db-winx64-10.11.5/target/mariaDB4j-db-winx64-10.11.5.1.pom.asc to /home/vorburger/git/github.com/vorburger/MariaDB4j/DBs/mariaDB4j-db-10.11.5/mariaDB4j-db-winx64-10.11.5/target/nexus-staging/staging/12bb4759cb85ae/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5.1/mariaDB4j-db-winx64-10.11.5.1.pom.asc
[INFO] Installing /home/vorburger/git/github.com/vorburger/MariaDB4j/DBs/mariaDB4j-db-10.11.5/mariaDB4j-db-winx64-10.11.5/target/mariaDB4j-db-winx64-10.11.5.1-sources.jar.asc to /home/vorburger/git/github.com/vorburger/MariaDB4j/DBs/mariaDB4j-db-10.11.5/mariaDB4j-db-winx64-10.11.5/target/nexus-staging/staging/12bb4759cb85ae/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5.1/mariaDB4j-db-winx64-10.11.5.1-sources.jar.asc
[INFO] Performing remote staging...
[INFO]
[INFO]  * Remote staging into staging profile ID "12bb4759cb85ae"
[INFO]  * Created staging repository with ID "chvorburger-1058".
[INFO]  * Staging repository at https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1058
[INFO]  * Uploading locally staged artifacts to profile ch.vorburger
Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1058/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5.1/mariaDB4j-db-winx64-10.11.5.1.jar.asc
Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1058/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5.1/mariaDB4j-db-winx64-10.11.5.1.jar.asc (833 B at 1.1 kB/s)
Downloading from ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1058/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/maven-metadata.xml
Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1058/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/maven-metadata.xml
Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1058/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/maven-metadata.xml (329 B at 550 B/s)
Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1058/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5.1/mariaDB4j-db-winx64-10.11.5.1-sources.jar.asc
Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1058/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5.1/mariaDB4j-db-winx64-10.11.5.1-sources.jar.asc (833 B at 2.8 kB/s)
Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1058/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5.1/mariaDB4j-db-winx64-10.11.5.1.pom.asc
Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1058/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5.1/mariaDB4j-db-winx64-10.11.5.1.pom.asc (833 B at 2.8 kB/s)
Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1058/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5/mariaDB4j-db-winx64-10.11.5.jar
Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1058/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5/mariaDB4j-db-winx64-10.11.5.jar (7.9 MB at 4.8 MB/s)
Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1058/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5/mariaDB4j-db-winx64-10.11.5.pom
Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1058/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5/mariaDB4j-db-winx64-10.11.5.pom (2.2 kB at 3.7 kB/s)
Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1058/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5.1/mariaDB4j-db-winx64-10.11.5.1.jar
Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1058/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5.1/mariaDB4j-db-winx64-10.11.5.1.jar (39 MB at 19 MB/s)
Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1058/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5.1/mariaDB4j-db-winx64-10.11.5.1.pom
Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1058/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5.1/mariaDB4j-db-winx64-10.11.5.1.pom (1.9 kB at 3.2 kB/s)
Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1058/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5.1/mariaDB4j-db-winx64-10.11.5.1-sources.jar
Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1058/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5.1/mariaDB4j-db-winx64-10.11.5.1-sources.jar (2.5 kB at 3.7 kB/s)
Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1058/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5/mariaDB4j-db-winx64-10.11.5.pom.asc
Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1058/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5/mariaDB4j-db-winx64-10.11.5.pom.asc (833 B at 2.8 kB/s)
Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1058/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5/mariaDB4j-db-winx64-10.11.5.jar.asc
Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1058/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5/mariaDB4j-db-winx64-10.11.5.jar.asc (833 B at 2.8 kB/s)
Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1058/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5/mariaDB4j-db-winx64-10.11.5-sources.jar.asc
Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1058/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5/mariaDB4j-db-winx64-10.11.5-sources.jar.asc (833 B at 2.9 kB/s)
Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1058/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5/mariaDB4j-db-winx64-10.11.5-sources.jar
Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1058/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5/mariaDB4j-db-winx64-10.11.5-sources.jar (2.5 kB at 3.1 kB/s)
[INFO]  * Upload of locally staged artifacts finished.
[INFO]  * Closing staging repository with ID "chvorburger-1058".

Waiting for operation to complete...
...........

[INFO] Remote staged 1 repositories, finished with success.
[INFO] Remote staging repositories are being released...

Waiting for operation to complete...
....

[ERROR]
[ERROR] Nexus Staging Rules Failure Report
[ERROR] ==================================
[ERROR]
[ERROR] Repository "chvorburger-1058" failures
[ERROR]   Rule "RepositoryWritePolicy" failures
[ERROR]     * Artifact updating: Repository ='releases:Releases' does not allow updating artifact='/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5/mariaDB4j-db-winx64-10.11.5.pom'
[ERROR]     * Artifact updating: Repository ='releases:Releases' does not allow updating artifact='/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5/mariaDB4j-db-winx64-10.11.5.jar'
[ERROR]     * Artifact updating: Repository ='releases:Releases' does not allow updating artifact='/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5/mariaDB4j-db-winx64-10.11.5-sources.jar'

Reading https://maven.apache.org/pom.html#version-order-specification, I suspect the "correct" (?) solution to this is to use a "version qualifier" and release it as a 10.11.5-fix1? I have now released it (the Windows binary only; the Linux one is fine) as that. I'll adapt the dependency and respective line in code accordingly in #772; here's the log from mvn deploy for this 10.11.5-fix1:

[INFO] --- install:3.1.0:install (default-install) @ mariaDB4j-db-winx64 ---
[INFO] Installing /home/vorburger/git/github.com/vorburger/MariaDB4j/DBs/mariaDB4j-db-10.11.5/mariaDB4j-db-winx64-10.11.5/pom.xml to /home/vorburger/.m2/repository/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5-fix1/mariaDB4j-db-winx64-10.11.5-fix1.pom
[INFO] Installing /home/vorburger/git/github.com/vorburger/MariaDB4j/DBs/mariaDB4j-db-10.11.5/mariaDB4j-db-winx64-10.11.5/target/mariaDB4j-db-winx64-10.11.5-fix1.jar to /home/vorburger/.m2/repository/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5-fix1/mariaDB4j-db-winx64-10.11.5-fix1.jar
[INFO] Installing /home/vorburger/git/github.com/vorburger/MariaDB4j/DBs/mariaDB4j-db-10.11.5/mariaDB4j-db-winx64-10.11.5/target/mariaDB4j-db-winx64-10.11.5-fix1-sources.jar to /home/vorburger/.m2/repository/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5-fix1/mariaDB4j-db-winx64-10.11.5-fix1-sources.jar
[INFO] Installing /home/vorburger/git/github.com/vorburger/MariaDB4j/DBs/mariaDB4j-db-10.11.5/mariaDB4j-db-winx64-10.11.5/target/mariaDB4j-db-winx64-10.11.5-fix1.jar.asc to /home/vorburger/.m2/repository/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5-fix1/mariaDB4j-db-winx64-10.11.5-fix1.jar.asc
[INFO] Installing /home/vorburger/git/github.com/vorburger/MariaDB4j/DBs/mariaDB4j-db-10.11.5/mariaDB4j-db-winx64-10.11.5/target/mariaDB4j-db-winx64-10.11.5-fix1.pom.asc to /home/vorburger/.m2/repository/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5-fix1/mariaDB4j-db-winx64-10.11.5-fix1.pom.asc
[INFO] Installing /home/vorburger/git/github.com/vorburger/MariaDB4j/DBs/mariaDB4j-db-10.11.5/mariaDB4j-db-winx64-10.11.5/target/mariaDB4j-db-winx64-10.11.5-fix1-sources.jar.asc to /home/vorburger/.m2/repository/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5-fix1/mariaDB4j-db-winx64-10.11.5-fix1-sources.jar.asc
[INFO]
[INFO] --- nexus-staging:1.6.13:deploy (injected-nexus-deploy) @ mariaDB4j-db-winx64 ---
[INFO] Performing local staging (local stagingDirectory="/home/vorburger/git/github.com/vorburger/MariaDB4j/DBs/mariaDB4j-db-10.11.5/mariaDB4j-db-winx64-10.11.5/target/nexus-staging/staging")...
[INFO]  + Using server credentials "ossrh" from Maven settings.
[INFO]  * Connected to Nexus at https://oss.sonatype.org:443/, is version 2.15.1-02 and edition "Professional"
[INFO]  * Using staging profile ID "12bb4759cb85ae" (matched by Nexus).
[INFO] Installing /home/vorburger/git/github.com/vorburger/MariaDB4j/DBs/mariaDB4j-db-10.11.5/mariaDB4j-db-winx64-10.11.5/target/mariaDB4j-db-winx64-10.11.5-fix1.jar to /home/vorburger/git/github.com/vorburger/MariaDB4j/DBs/mariaDB4j-db-10.11.5/mariaDB4j-db-winx64-10.11.5/target/nexus-staging/staging/12bb4759cb85ae/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5-fix1/mariaDB4j-db-winx64-10.11.5-fix1.jar
[INFO] Installing /home/vorburger/git/github.com/vorburger/MariaDB4j/DBs/mariaDB4j-db-10.11.5/mariaDB4j-db-winx64-10.11.5/pom.xml to /home/vorburger/git/github.com/vorburger/MariaDB4j/DBs/mariaDB4j-db-10.11.5/mariaDB4j-db-winx64-10.11.5/target/nexus-staging/staging/12bb4759cb85ae/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5-fix1/mariaDB4j-db-winx64-10.11.5-fix1.pom
[INFO] Installing /home/vorburger/git/github.com/vorburger/MariaDB4j/DBs/mariaDB4j-db-10.11.5/mariaDB4j-db-winx64-10.11.5/target/mariaDB4j-db-winx64-10.11.5-fix1-sources.jar to /home/vorburger/git/github.com/vorburger/MariaDB4j/DBs/mariaDB4j-db-10.11.5/mariaDB4j-db-winx64-10.11.5/target/nexus-staging/staging/12bb4759cb85ae/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5-fix1/mariaDB4j-db-winx64-10.11.5-fix1-sources.jar
[INFO] Installing /home/vorburger/git/github.com/vorburger/MariaDB4j/DBs/mariaDB4j-db-10.11.5/mariaDB4j-db-winx64-10.11.5/target/mariaDB4j-db-winx64-10.11.5-fix1.jar.asc to /home/vorburger/git/github.com/vorburger/MariaDB4j/DBs/mariaDB4j-db-10.11.5/mariaDB4j-db-winx64-10.11.5/target/nexus-staging/staging/12bb4759cb85ae/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5-fix1/mariaDB4j-db-winx64-10.11.5-fix1.jar.asc
[INFO] Installing /home/vorburger/git/github.com/vorburger/MariaDB4j/DBs/mariaDB4j-db-10.11.5/mariaDB4j-db-winx64-10.11.5/target/mariaDB4j-db-winx64-10.11.5-fix1.pom.asc to /home/vorburger/git/github.com/vorburger/MariaDB4j/DBs/mariaDB4j-db-10.11.5/mariaDB4j-db-winx64-10.11.5/target/nexus-staging/staging/12bb4759cb85ae/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5-fix1/mariaDB4j-db-winx64-10.11.5-fix1.pom.asc
[INFO] Installing /home/vorburger/git/github.com/vorburger/MariaDB4j/DBs/mariaDB4j-db-10.11.5/mariaDB4j-db-winx64-10.11.5/target/mariaDB4j-db-winx64-10.11.5-fix1-sources.jar.asc to /home/vorburger/git/github.com/vorburger/MariaDB4j/DBs/mariaDB4j-db-10.11.5/mariaDB4j-db-winx64-10.11.5/target/nexus-staging/staging/12bb4759cb85ae/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5-fix1/mariaDB4j-db-winx64-10.11.5-fix1-sources.jar.asc
[INFO] Performing remote staging...
[INFO]
[INFO]  * Remote staging into staging profile ID "12bb4759cb85ae"
[INFO]  * Created staging repository with ID "chvorburger-1059".
[INFO]  * Staging repository at https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1059
[INFO]  * Uploading locally staged artifacts to profile ch.vorburger
Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1059/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5-fix1/mariaDB4j-db-winx64-10.11.5-fix1-sources.jar.asc
Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1059/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5-fix1/mariaDB4j-db-winx64-10.11.5-fix1-sources.jar.asc (833 B at 1.1 kB/s)
Downloading from ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1059/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/maven-metadata.xml
Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1059/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/maven-metadata.xml
Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1059/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/maven-metadata.xml (335 B at 591 B/s)
Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1059/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5-fix1/mariaDB4j-db-winx64-10.11.5-fix1-sources.jar
Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1059/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5-fix1/mariaDB4j-db-winx64-10.11.5-fix1-sources.jar (2.5 kB at 3.8 kB/s)
Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1059/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5-fix1/mariaDB4j-db-winx64-10.11.5-fix1.pom.asc
Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1059/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5-fix1/mariaDB4j-db-winx64-10.11.5-fix1.pom.asc (833 B at 3.0 kB/s)
Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1059/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5-fix1/mariaDB4j-db-winx64-10.11.5-fix1.jar
Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1059/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5-fix1/mariaDB4j-db-winx64-10.11.5-fix1.jar (20 MB at 9.8 MB/s)
Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1059/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5-fix1/mariaDB4j-db-winx64-10.11.5-fix1.pom
Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1059/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5-fix1/mariaDB4j-db-winx64-10.11.5-fix1.pom (1.9 kB at 3.4 kB/s)
Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1059/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5-fix1/mariaDB4j-db-winx64-10.11.5-fix1.jar.asc
Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1059/ch/vorburger/mariaDB4j/mariaDB4j-db-winx64/10.11.5-fix1/mariaDB4j-db-winx64-10.11.5-fix1.jar.asc (833 B at 3.0 kB/s)
[INFO]  * Upload of locally staged artifacts finished.
[INFO]  * Closing staging repository with ID "chvorburger-1059".

Waiting for operation to complete...
...........

[INFO] Remote staged 1 repositories, finished with success.
[INFO] Remote staging repositories are being released...

Waiting for operation to complete...
......

[INFO] Remote staging repositories released.
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  01:20 min
[INFO] Finished at: 2023-09-19T00:52:35+02:00
[INFO] ------------------------------------------------------------------------

@TheKnowles
Copy link
Contributor Author

That's fascinating, I did not realize a point release would not work.

vorburger added a commit that referenced this pull request Sep 18, 2023
includes bumping MariaDB v10.11.5 Windows binary to 10.11.5-fix1;
see #771 for details.
vorburger pushed a commit that referenced this pull request Sep 18, 2023
vorburger added a commit that referenced this pull request Sep 18, 2023
includes bumping MariaDB v10.11.5 Windows binary to 10.11.5-fix1;
see #771 for details.
@vorburger
Copy link
Collaborator

That's fascinating, I did not realize a point release would not work.

Fascinating is one way to describe the mess that Maven versions are... I just hope (not tested!) that -fix1 will also work for Gradle, et al! 🤣

now released it (the Windows binary only; the Linux one is fine) as that (10.11.5-fix1)

And with that, #772 was green, and got merged. With that, I am (finally!) closing this PR, because I squashed the 4 commits from here into 78d17f8, which is now merged to the main branch.

@vorburger vorburger closed this Sep 18, 2023
This was referenced Sep 18, 2023
@TheKnowles
Copy link
Contributor Author

Thanks for the review and merge! In retrospect, I should have done a full run on an actual Windows machine. I was surprised how different the maria releases are, I had only done the simulated unit test run from a linux machine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants