NativeOrNativeSourcesBuild deprecated: recommended way to replace it?

[apupier]

Hi,

I noticed that https://github.com/quarkusio/quarkus/blame/main/core/deployment/src/main/java/io/quarkus/deployment/pkg/steps/NativeOrNativeSourcesBuild.java is deprecated since Quarkus 3.10.
From the Javadoc, In the future, it will be possible to request multiple output types. It is not clear to me by what it should be replaced.

The Quarkus 3.10 does not contain information on this deprecation https://quarkus.io/blog/quarkus-3-10-0-released/

Do you have some examples?

regards,

[dmlloyd]

I'll answer since I'm the one who did it :-)

Internally, we have the concept of "some kind of output", as in "when you build this application, I want an output of kind X or Y or Z". The problem with this idea is that we actually often need more than one kind of output, say X and Y, or X and Z. To make matters worse, sometimes, to output type Z we have to force type Y instead of X.

The idea would then be to reassess this approach and instead of choosing X or Y with a side of Z and/or W possibly forcing Y and rejecting X sometimes, we would have a system whereby the outputs are requested additively, so I can request X and Z, and if Z requires Y, then Y is automatically added, so we get X, Y, and Z.

This approach solves several internal issues about how native images are built and how packaging is chosen, and removes a bit of hard-coding as well. Unfortunately it's been pretty tricky to implement so far. My hope is to make some progress on this during Q4 or Q1.

[apupier]

Thanks for the explanation.
If I understand well, currently there is no replacement available but it is planned for Q42025 or Q12026.
Is there an issue opened that I can follow on this topic?