Merge `quarkus/[service|server]` modules in `polaris-server`

[jbonofre]

All quarkus modules can be merged together in a single module. This module should be polaris-server directly (no need to keep Quarkus there).

[snazy]

No, those cannot (and should not) be merged.

[snazy]

/cc @adutra

[jbonofre]

@snazy It has been discussed with @adutra and yes it's possible and should be done.

[jbonofre]

To be clear, the intent here is to "merge" the beans but still have a default module with just application.properties.

[snazy]

To be clear, the intent here is to "merge" the beans but still have a default module with just application.properties.

This is not what the title says: "merge admin-tool + server (+ service)". Those are two different executables

[jbonofre]

Ah yes, the idea is to merge service and server as app. admin is still "separated". Sorry I wasn't clear enough.

[adutra]

Yes, we can (and probably should) merge service and server. But we should not touch admin or defaults.

I already have the change ready btw, but it's waiting on #987.

Also, the change will introduce a tricky issue related to docker images and integration tests. It's manageable, but It would maybe be easier if we waited for quarkusio/quarkus#46232.

[jbonofre]

@adutra thanks for your update. I agree. The intent of this GitHub Issue is just to track it. I hope you don't mind: I assigned the issue to you as you already have the change ready.

[dimas-b]

What will the unified polaris-server module publish (to Maven)? Will it be the quarkus fat jar or a lean jar with just local classes?

How can downstream projects reuse service classes without pulling too much extra stuff?