Skip to content

Commit

Permalink
Vert.x Hazelcast works with bot HZ 4.x and 5.x but still references 4…
Browse files Browse the repository at this point in the history
….2.8 by default while it is tested in CI with 4.2.8 and 5.3.5.

Since HZ 4.x is not supported anymore in community and the 4.2.8 has CVE it is reasonnable to depend on 5.3.5 in our pom while testing with 4.3.8 and 5.3.5.
  • Loading branch information
vietj committed May 23, 2024
1 parent 1023bcf commit e4875fc
Show file tree
Hide file tree
Showing 2 changed files with 7 additions and 1 deletion.
2 changes: 1 addition & 1 deletion pom.xml
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@
<properties>
<stack.version>4.5.8-SNAPSHOT</stack.version>
<asciidoc.dir>${project.basedir}/src/main/asciidoc</asciidoc.dir>
<hazelcast.version>4.2.8</hazelcast.version>
<hazelcast.version>5.3.5</hazelcast.version>
<hazelcast-kubernetes.version>2.2.3</hazelcast-kubernetes.version>
<jar.manifest>${project.basedir}/src/main/resources/META-INF/MANIFEST.MF</jar.manifest>
</properties>
Expand Down
6 changes: 6 additions & 0 deletions src/main/asciidoc/index.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -45,6 +45,12 @@ when you are creating your Vert.x instance, for example:
{@link examples.Examples#example1()}
----

== Hazelcast version

Since Vert.x 4.5.8, the version of the Hazelcast dependency is changed to 5.3 since Hazelcast 4 is not anymore supported and 4.2.8 has known vulnerabilities (CVE-2023-45860, CVE-2023-45859, CVE-2023-33265, CVE-2023-33264).

This cluster manager remains tested with Hazelcast 4.2.8 and 5.3, so 4.2.8 remains supported, the Hazelcast version must be explicitly set to 4.2.8 if needed until an upgrade can be achieved.

[[configcluster]]
== Configuring this cluster manager

Expand Down

0 comments on commit e4875fc

Please sign in to comment.