mvn-repo | Maven repository for eXist compiled artifacts | Build Tool library

The problem was indeed in the maven repository link. It seems that the dependencies have changed recently.

In my case the solution was to remove the repository in POM that caused trouble, namely

When using Github's Site Plugin for maven, repositoryName has to be the name of the repository only, in this case mavenRepoTest.

Add the server to your maven properties like this:

As long as you see nbauma109@github.com, you can be sure an SSH push will fail (from command-line or maven)

A GitHub SSH URL would always use the remote user 'git': git@github.com:..., never the actual GitHub user account name: your public key registered to said GitHub account is suppose to authenticate you.

So start testing with:

• A solution: use version 0.13.18 of SBT instead. That is still on the repository, while version 0.13.17 has already been deleted.

  Just change the version within your project/build.properties: to

  sbt.version=0.13.18. As mentioned in that other post you also need to update the sbt launcher to version 0.13.18.

• Recommended solution: Try changing the sbt version to 1.X.X. Versions 0.13.X are no longer supported (see in scala-sbt docs). Note that SBT 1.X.X introduced breaking changes, so you would need to follow their guide for migrating from 0.13.X.

It looks like maven-s3-wagon doesn't play well with Java 11. I swapped out the maven-s3-wagon wagon for the aws-maven wagon and it resolved my issue

Prior wagon

First of all, for some reason you apply both the maven plugin and the maven-publish plugin. Both plugins do basically the same, but the first one was deprecated a long time ago. You should decide which plugin to use and I suggest to use the maven-publish plugin.

Nevertheless, lets take a look at the documentation of the old maven plugin. It says:

Maven Element: artifactId
Default value: uploadTask.repositories.mavenDeployer.pom.artifactId (if set) or archiveTask.archiveBaseName

And later:

When you set the archiveTask.archiveBaseName property to a value other than the default, you’ll also have to set uploadTask.repositories.mavenDeployer.pom.artifactId to the same value. Otherwise, the project at hand may be referenced with the wrong artifact ID from generated POMs for other projects in the same build.

Here, mavenDeployer refers to a deprecated method that gets added to the RepositoryHandler behind repositories. It seems like it is required to use this deprecated way to specify the target repository instead using the maven method you used. Sadly, there is probably no way to use the AWS authentication and the s3 protocol with this old interface.

Let's now take a look at the new maven-publish plugin. With this plugin, you no longer define artifacts and configure Upload tasks. Instead, you define publications and repositories and the plugin will generate a task for each combination of a publication and a repository:

For eXist-db 5.x.x you need two repositories:

1. Maven Central for the eXist-db artifacts themselves.
2. eXist-db's Repository (http://repo.evolvedbinary.com/repository/exist-db/) for some third-party artifacts which cannot be published to Maven Central as they do not meet the requirements for Maven Central.