Skip to content
Open
Changes from all 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
2 changes: 1 addition & 1 deletion spannerlib/wrappers/spannerlib-java/pom.xml
Original file line number Diff line number Diff line change
Expand Up @@ -69,7 +69,7 @@
<dependency>
<groupId>io.netty</groupId>
<artifactId>netty-transport-native-epoll</artifactId>
<version>4.2.12.Final</version>
<version>4.2.13.Final</version>
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

Updating only the netty-transport-native-epoll version while other Netty dependencies are likely managed by the grpc-bom (line 40) can lead to version mismatches in the classpath. Netty requires all its modules (such as netty-common, netty-transport, and netty-buffer) to have the exact same version to avoid runtime errors like NoSuchMethodError. When updating dependencies, especially those not managed by a BOM, verify the version's release date to ensure it is current and compatible with other libraries. To ensure consistency, it is recommended to also update the other Netty dependencies to 4.2.13.Final, or better yet, add the netty-bom to the dependencyManagement section with the desired version.

References
  1. When updating dependencies, especially those not managed by a BOM, verify the version's release date to ensure it is current and compatible with other libraries.

</dependency>
<!-- Dependencies for using C library -->
<dependency>
Expand Down
Loading