Skip to content
Closed
Changes from 5 commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions pom.xml
Original file line number Diff line number Diff line change
Expand Up @@ -75,7 +75,7 @@
-->
<stax2-api.version>4.2.1</stax2-api.version>

<junit-bom.version>5.11.2</junit-bom.version>
<junit-bom.version>5.12.0</junit-bom.version>
<testcontainers-bom.version>1.20.5</testcontainers-bom.version>
<hikaricp.version>4.0.3</hikaricp.version>
<awaitility.version>4.3.0</awaitility.version>
Expand All @@ -84,7 +84,7 @@
<maven-javadoc-plugin.version>3.10.1</maven-javadoc-plugin.version>
<maven-gpg-plugin.version>3.2.7</maven-gpg-plugin.version>
<central-publishing-maven-plugin.version>0.5.0</central-publishing-maven-plugin.version>
<native-maven-plugin.version>0.10.5</native-maven-plugin.version>
<native-maven-plugin.version>0.10.6</native-maven-plugin.version>
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do you need to change native-maven-plugin.version?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You're right, the native-maven-plugin version change wasn't necessary for the JUnit upgrade. I've reverted it back to 0.10.5 and kept only the JUnit upgrade from 5.11.2 to 5.12.0. The JUnit compatibility issue with GraalVM native-build-tools was resolved independently of the plugin version. See commit 5159788.

<maven-resources-plugin.version>3.3.1</maven-resources-plugin.version>
<maven-compiler-plugin.version>3.13.0</maven-compiler-plugin.version>
<maven-surefire-plugin.version>3.5.0</maven-surefire-plugin.version>
Expand Down