Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JettyHttpContainerFactory no longer being exposed. #4739

Closed
hunterbreathat-wk opened this issue Mar 2, 2021 · 3 comments
Closed

JettyHttpContainerFactory no longer being exposed. #4739

hunterbreathat-wk opened this issue Mar 2, 2021 · 3 comments

Comments

@hunterbreathat-wk
Copy link

👋🏻 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.

@senivam
Copy link
Contributor

senivam commented Mar 3, 2021

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.

@hunterbreathat-wk
Copy link
Author

Would it be possible for a SNAPSHOT to be released for 3.0.2? If not what is the projected release timeline?

@jansupol
Copy link
Contributor

jansupol commented Oct 6, 2021

Fixed by #4709

@jansupol jansupol closed this as completed Oct 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants