added netty resolver and upgraded solace java version to 1.7.0

SolaceLabs · Oct 10, 2024 · 76d521a · 76d521a
1 parent dedb3b1
commit 76d521a
Show file tree

Hide file tree

Showing 2 changed files with 10 additions and 1 deletion.
diff --git a/pom.xml b/pom.xml
@@ -38,7 +38,7 @@
     <project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
     <quarkus.version>3.8.6</quarkus.version>
 
-    <solace.version>1.4.0</solace.version>
+    <solace.version>1.7.0</solace.version>
 
     <assertj-core.version>3.24.2</assertj-core.version>
     <weld.version>5.1.2.Final</weld.version>

diff --git a/...solace-client/deployment/src/main/java/com/solace/quarkus/deployment/SolaceProcessor.java b/...solace-client/deployment/src/main/java/com/solace/quarkus/deployment/SolaceProcessor.java
@@ -3,6 +3,7 @@
 import java.util.Optional;
 import java.util.function.Function;
 
+import io.quarkus.deployment.builditem.nativeimage.NativeImageResourceBuildItem;
 import jakarta.enterprise.context.ApplicationScoped;
 import jakarta.enterprise.inject.Instance;
 
@@ -104,4 +105,12 @@ HealthBuildItem addHealthCheck(SolaceBuildTimeConfig buildTimeConfig) {
                 buildTimeConfig.health().enabled());
     }
 
+    /**
+     * `Version.identify()` in netty-common uses the resource to determine the version of netty.
+     */
+    @BuildStep
+    NativeImageResourceBuildItem nettyVersions() {
+        return new NativeImageResourceBuildItem("META-INF/io.netty.versions.properties");
+    }
+
 }