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
👋🏻 In transitioning to version 3.0.1 of jersey-containers-jetty-http it was noticed that
server =JettyHttpContainerFactory.createServer(baseUri, config)
no longer functions. This is due to that class not being exposed, which is the opposite of what the documentation suggests, found here under section 4.5.1.3. This was also not listed as a breaking change, I currently have a workaround (copy the setup from that class definition).
I'm not sure if this was intentional on release or not.
PS. The JettyHttpContainerFactory.class is included in the meta of the lib but not actually exposed outwards.
The text was updated successfully, but these errors were encountered:
The issue with Jetty multi-release jar is fixed under this issue: #4655, the fix shall become available under Jersey 3.0.2 version which will be released in the nearest feature.
👋🏻 In transitioning to version
3.0.1
ofjersey-containers-jetty-http
it was noticed thatno longer functions. This is due to that class not being exposed, which is the opposite of what the documentation suggests, found here under section 4.5.1.3. This was also not listed as a breaking change, I currently have a workaround (copy the setup from that class definition).
I'm not sure if this was intentional on release or not.
PS. The JettyHttpContainerFactory.class is included in the meta of the lib but not actually exposed outwards.
The text was updated successfully, but these errors were encountered: