Fix dependencies for Grizzly connector #4917
Comments
zUniQueX
added a commit
to zUniQueX/jersey
that referenced
this issue
Dec 2, 2021
Exclude declared dependencies with other versions from grizzly-http-client Signed-off-by: Steffen Nießing <[email protected]>
jansupol
pushed a commit
that referenced
this issue
Dec 6, 2021
Exclude declared dependencies with other versions from grizzly-http-client Signed-off-by: Steffen Nießing <[email protected]>
|
@jansupol As the next 3.0.x version is released, are there any release plans for 2.36 to get this fixed? |
|
Currently, only a dot release can be made, until a release review (which needs to be done once a year). We will go through the release review and we plan the release for March. |
|
Okay, thanks for clarifying this |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
grizzly-connectordeclares dependencies forgrizzly-websocketsandconnection-pool, whilegrizzly-http-clientalready has dependencies on those. This is causing conflicts at the dependency convergence in the maven enforcer plugin in projects using this connector sincegrizzly-http-clientuses the dependency version 2.4.3, while the pom of Jersey defines the version as 2.4.4.Would it be possible to either remove these dependencies or to add exclusions for them to the dependency declaration of
grizzly-http-client? Else one cannot use this connector when having dependency convergence enabled.The text was updated successfully, but these errors were encountered: