RESTEasy Reactive dependency added to deployment classpath of nearly all Quarkus apps about quarkus

[geoand]

I removed the dependency in question and as far as I can tell things continue to work...

[geoand]

I already have an open PR for it 🙂

[quarkus-bot]

/cc @FroMage (resteasy-reactive), @geoand (resteasy-reactive), @stuartwdouglas (resteasy-reactive)

[maxandersen]

yeah that is not a good thing.

[geoand]

I don't know exactly why quarkus-rest-server-spi-deployment depends on io.quarkus.resteasy.reactive:resteasy-reactive-processor but that's probably something that we need to fix.

Unfortunately this is not really possible as the SPI introduces build items that allow customization of server types.

@phillip-kruger what exactly was the reason you had to depend on quarkus-rest-server-spi-deployment?

[phillip-kruger]

I'll have a look. I can't remember:)

[phillip-kruger]

I can not recall why, but definitely not needed, we can just remove that. Just to double check my understanding, that was only depending on a deployment module, so it should not have brought anything into the runtime app of the user ?

[gsmet]

Yes as I Said, it was only in the deployment classpath.
I noticed it because I built an app that is not using RR and when I updated Quarkus, it downloaded the RR jar.

Nice if we can drop it.

[phillip-kruger]

Ok great, I just wanted to make sure my understanding is correct. I'll prepare a pr to remove it

[phillip-kruger]

Sorry - i did not see :) I'll close mine.

[geoand]

NP!