apicurio Runner jar is missing from tarball 3.15 onwards

[anirban1989]

We use the runner jar packaged in the tarball assets to run the same in a docker container . We see this version missing from 3.1.5 onwards

3.1.4
--- lib
--- meta
--- apicurio-registry-app-3.1.4-runner.jar

3.1.5/3.1.6
meta
quarkus-app
quarkus-app\app
quarkus-app\lib
quarkus-app\quarkus
quarkus-app\quarkus-run.jar
quarkus-app\quarkus-app-dependencies.txt
quarkus-app\app\apicurio-registry-app-3.1.6.jar

Which file can be used as the new runner

[anirban1989]

From this PR #6989 , i understand now that from 3.1.6 the project build to create a quarkus fast jar which will be available at the path quarkus-app/quarkus-run.jar in the tarball . Please confirm if this is the runner to be used .

[carlesarnal]

Hi @anirban1989,
You're correct! Starting with version 3.1.5, Apicurio Registry switched to Quarkus "fast-jar" packaging (introduced in PR #6989 with the Quarkus 3.27 upgrade).

The new runner jar location is:

quarkus-app/quarkus-run.jar
To run the registry, use:

java -jar quarkus-app/quarkus-run.jar
Important notes:

• The entire quarkus-app/ directory structure must be preserved - the quarkus-run.jar depends on the sibling directories (lib/, app/, quarkus/) within quarkus-app/
• All the same configuration options (like -Dapicurio.storage.kind=sql) work exactly as before

This fast-jar format provides faster startup times compared to the previous uber-jar packaging and is the Quarkus standard, which is why this change was made.