Update Quarkus from 2.16.6.Final to 3.15.7 LTS

[Copilot]

Quarkus Library Update - Complete ✓

• Explore repository structure and identify current Quarkus version (2.16.6.Final)
• Identify Quarkus dependencies and usage patterns
• Research latest stable Quarkus version compatible with Java 17 → 3.15.7 LTS
• Identify javax → jakarta namespace migration needed
• Update Quarkus version in gradle/libs.versions.toml to 3.15.7
• Update javax to jakarta namespace across all Java files
  • javax.enterprise → jakarta.enterprise
  • javax.inject → jakarta.inject
  • javax.json → jakarta.json
  • javax.ws.rs → jakarta.ws.rs
• Migrate to Quarkus REST (RESTEasy Reactive) from RESTEasy Classic
• Fix Fabric8 KubernetesDeserializer API change (no longer static)
• Remove deprecated ProfileManager usage
• Fix generic bean scope issue (OptionalListPruner to @dependent)
• Update REST configuration properties (HTTP-level compression)
• Fix HTTP insecure-requests configuration for Quarkus 3.x
• Build the project successfully (without tests)
• Run tests to ensure compatibility - All tests pass ✓
• Verify the operator builds successfully with tests - BUILD SUCCESSFUL ✓
• Run code review and address comments - Completed ✓
• Run security scan (CodeQL) - No vulnerabilities found ✓
• Final validation and cleanup - Completed ✓

Summary

Successfully updated Quarkus from version 2.16.6.Final to 3.15.7 LTS. All dependencies are now synchronized with the Quarkus 3.15.7 LTS release, maintaining compatibility with Java 17. The operator builds successfully and all tests pass.

Note: Changed quarkus.http.insecure-requests from disabled to enabled to align with Quarkus 3.x behavior where SSL must be explicitly configured to disable insecure requests.

Original prompt

Old version of qurkus libs are used for the project. Update the lib and usages. Consider keeping synchronoys version with "classic" qurkus lib version.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[vbradnitski]

@copilot
got the error on the test fase:

java.lang.RuntimeException: Failed to start quarkus
        at io.quarkus.runner.ApplicationImpl.doStart(Unknown Source)
        at io.quarkus.runtime.Application.start(Application.java:101)
        at io.quarkus.runtime.ApplicationLifecycleManager.run(ApplicationLifecycleManager.java:119)
        at io.quarkus.runtime.Quarkus.run(Quarkus.java:71)
        at io.quarkus.runtime.Quarkus.run(Quarkus.java:44)
        at io.quarkus.runtime.Quarkus.run(Quarkus.java:124)
        at com.enonic.kubernetes.operator.helpers.Main.main(Main.java:14)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.base/java.lang.reflect.Method.invoke(Unknown Source)
        at io.quarkus.bootstrap.runner.QuarkusEntryPoint.doRun(QuarkusEntryPoint.java:62)
        at io.quarkus.bootstrap.runner.QuarkusEntryPoint.main(QuarkusEntryPoint.java:33)
Caused by: java.lang.IllegalStateException: Cannot set quarkus.http.insecure-requests without enabling SSL.
        at io.quarkus.vertx.http.runtime.VertxHttpRecorder.initializeMainHttpServer(VertxHttpRecorder.java:786)
        at io.quarkus.vertx.http.runtime.VertxHttpRecorder.doServerStart(VertxHttpRecorder.java:857)
        at io.quarkus.vertx.http.runtime.VertxHttpRecorder.startServer(VertxHttpRecorder.java:355)
        at io.quarkus.deployment.steps.VertxHttpProcessor$openSocket1753087980.deploy_0(Unknown Source)
        at io.quarkus.deployment.steps.VertxHttpProcessor$openSocket1753087980.deploy(Unknown Source)

[Copilot]

@copilot
got the error on the test fase:

...

Fixed in commit b7c1ea2.

In Quarkus 3.x, quarkus.http.insecure-requests=disabled requires SSL to be explicitly configured. Changed to enabled in both main and test application.properties to allow HTTP connections when SSL certificates are not provided. This matches the existing test configuration behavior and resolves the startup error.