You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Both gRPC and netty come with a lot of modules that need to have the same version. Furthermore gRPC has netty shaded so any netty runtime dependencies on native bits need to also be aligned with whatever is shaded within gRPC.
In order to make sure all gRPC and netty dependencies (direct or transitive) are in the same version, the usual approach is to make use of BOMs.
The goal here would be to manage both the gRPC dependencies as well as the netty dependencies with BOMs.
Since java-spiffe itself also comes with multiple modules, it might be worthwhile to also publish a BOM so those versions are aligned.
Both gRPC and netty come with a lot of modules that need to have the same version. Furthermore gRPC has netty shaded so any netty runtime dependencies on native bits need to also be aligned with whatever is shaded within gRPC.
In order to make sure all gRPC and netty dependencies (direct or transitive) are in the same version, the usual approach is to make use of BOMs.
The goal here would be to manage both the gRPC dependencies as well as the netty dependencies with BOMs.
Since java-spiffe itself also comes with multiple modules, it might be worthwhile to also publish a BOM so those versions are aligned.
See also:
The text was updated successfully, but these errors were encountered: