Simple way to exclude quarkus-devtools-common transitive dependencies

[shawkins]

Description

Keycloak builds retain a runtime dependency on quarkus-devtools-common via quarkus-reactive-routes-deployment, which has a large transitive dependency footprint - including maven related dependencies.

However we cannot simply exclude quarkus-devtools-common because its classes are needed by classes mentioned in the quarkus-build-step.list file. None of those build steps are actually needed in the Keycloak distribution.

Tracking downstream as keycloak/keycloak#38665

cc @geoand @vmuzikar

Implementation ideas

No response

[geoand]

cc @aloubyansky

[vmuzikar]

Should this be a bug rather than an enhancement?

[mabartos]

@geoand @aloubyansky Hi guys, do you have any idea how it can be solved on the Quarkus side? Thanks!

[aloubyansky]

I'll review the options

[mabartos]

@aloubyansky Hello, what's the progress here? I see that PR #45053 creates some additional dev modules, but not related to the quarkus-reactive-routes-deployment and all others, right?

Do you expect to do some other work around this? And what is the plan for including it in the 3.20 LTS?

Thanks!

[aloubyansky]

Yes, I have a branch where I am doing more around this. This is definitely not going to be backported to 3.20 though.

[aloubyansky]

It's not really quarkus-reactive-routes-deployment but quarkus-vertx-http-deployment that pulls it in