Add qute-web to the platform

[ia3andy]

As this is now controlling Qute RESTEasy (Classic and Reactive) and this is a very important extension for the Quarkus Web story, Qute Web should be part of the Quarkus Platform.

When it's in the platform, we should unlist Qute RESTEasy (Classic and Reactive).

[quarkus-bot]

/cc @mkouba (qute)

[maxandersen]

will this extension be affected by the future suggested rename/change of removing reactive from names?

[ia3andy]

@aloubyansky how should we do this?

[aloubyansky]

if it's a single extension we could add it to the quarkus-bom in the platform.

[ia3andy]

@aloubyansky will that make it part of the paltform on code.quarkus.io

[aloubyansky]

Yes

[ia3andy]

ok so let's wait for the 3.0.0 of quarkus-qute-web and add it there :)

[ia3andy]

We will need to put qute-web in the platform in between the core release 3.6.0 and the platform release (because qute-web 3.0.0 will need to be released with 3.6.0 core).

@gsmet is there something specific to do in order to plan this?

[maxandersen]

Unlisting is just on code.quarkus ui, right?

The extension can still be referenced in cli and code.quarkus rest api ?

[ia3andy]

Yes

[ia3andy]

and also maybe for the extensions page @holly-cummins? I think it makes sense to unlist it from there to.

[ia3andy]

@maxandersen stupid question, why would it be a problem not to have it usable in CLI? Those extensions are useless by themselves as soon as we have the conditional system.

[ia3andy]

Yeah I tested quarkus-arc is not in quarkus.io/extensions (it's unlisted) which is a good thing

[mkouba]

if it's a single extension we could add it to the quarkus-bom in the platform.

@aloubyansky What exactly does it involve? Are there instructions pls?

[aloubyansky]

@mkouba it'd be done here https://github.com/quarkusio/quarkus-platform/blob/main/pom.xml#L183-L197

[mkouba]

@mkouba it'd be done here https://github.com/quarkusio/quarkus-platform/blob/main/pom.xml#L183-L197

Something like this? mkouba/quarkus-platform@4153dc1

[aloubyansky]

Yes

[maxandersen]

@maxandersen stupid question, why would it be a problem not to have it usable in CLI? Those extensions are useless by themselves as soon as we have the conditional system.

Only if you are on that specific version that has it - cli needs to continue to work for older versions. I don't know which extensions you are referring to as useless so can't answer your question fully.

[maxandersen]

will this extension be affected by the future suggested rename/change of removing reactive from names?

Didn't see reply to this - any concerns/actions there ?

[mkouba]

will this extension be affected by the future suggested rename/change of removing reactive from names?

Didn't see reply to this - any concerns/actions there ?

I don't think so. Except that we'll have to update the conditional dependencies on resteasy integration modules...

@ia3andy WDYT?

[ia3andy]

@maxandersen stupid question, why would it be a problem not to have it usable in CLI? Those extensions are useless by themselves as soon as we have the conditional system.

Only if you are on that specific version that has it - cli needs to continue to work for older versions. I don't know which extensions you are referring to as useless so can't answer your question fully.

Ok, the unlisted flag is platform induced so we are fine.

Regarding the change of name I don't think either, like Martin said

[rsvoboda]

Shouldn't be this mentioned in https://github.com/quarkusio/quarkus/wiki/Migration-Guide-3.6?
Or maybe even in https://quarkus.io/blog/quarkus-3-6-0-released/ (if edits are ok-ish)

[ia3andy]

Shouldn't be this mentioned in https://github.com/quarkusio/quarkus/wiki/Migration-Guide-3.6? Or maybe even in https://quarkus.io/blog/quarkus-3-6-0-released/ (if edits are ok-ish)

#37478 (comment)