Provide release artifacts in a public Maven repository

[nicow-odit]

Please publish the release artifacts to a public Maven repository, e.g. Maven Central, so that they can be easily consumed by Maven, Gradle, etc.

This is especially important due to the fact that tools like https://jitpack.io/ fail to circumvent this since there's a build dependency on the client (see https://jitpack.io/com/github/privacyidea/keycloak-provider/v1.1.0/build.log).

[nilsbehlen]

What are you doing with it that you would need it on mavencentral? If there is a good reason for it, we might consider it, but otherwise its just additional work.

[nicow-odit]

We're building a customized Keycloak Docker image consisting of several providers. This is done using Maven. The idea is to pull PrivacyIDEA's keycloak-provider using Maven's standard mechanisms as we do for other providers, unpack, customize some templates, re-package, and include it in the built Docker image.

[belfhi]

Out of curiosity @nicow-odit , how do you use maven during the docker build? I just curl all my providers... 😬

[nicow-odit]

It's the other way around: the Docker build is embedded in the Maven build. During the latter we build providers as sub-modules first that will be shipped in the final Docker image later. One of the sub-modules would be PrivacyIDEA's keycloak provider that also needs some customization. This is why it's not sufficient to just pull it in, but to define it as a (Maven) dependency to be able to compile and build against it.

[nilsbehlen]

https://central.sonatype.org/publish/publish-guide/