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

Upgrade Netty and expose Netty Context #3983

Merged
merged 3 commits into from
Apr 10, 2019
Merged

Upgrade Netty and expose Netty Context #3983

merged 3 commits into from
Apr 10, 2019

Conversation

juur
Copy link
Contributor

@juur juur commented Nov 2, 2018

Bumped netty version to latest
Updated API usage to match
Enhanced returned SecurityContext to include Netty information

Bumped netty version to latest
Updated API usage to match
Enhanced returned SecurityContext to include Netty information

Signed-off-by: Ian <[email protected]>
Signed-off-by: Ian <[email protected]>
@jansupol
Copy link
Contributor

jansupol commented Nov 2, 2018

There is a valid ECA on file for [email protected].

@juur
Copy link
Contributor Author

juur commented Nov 9, 2018

Does the CQ required label require me to do anything?

@jansupol
Copy link
Contributor

No, I think only committers can file CQs. Once Jersey goes through release review, we will deal with new CQs

@mkarg
Copy link
Member

mkarg commented Dec 29, 2018

@jansupol FYI I just tested it, and you are right: The Eclipse Committer Tools present a 404 to me when trying to file a CQ for Jersey, while it works for JAX-RS. So this is definitively a committers-only task.

@jansupol
Copy link
Contributor

jansupol commented Mar 15, 2019

Created CQ for Netty 4.1.31.FINAL

@jansupol
Copy link
Contributor

jansupol commented Apr 9, 2019

CQ has been approved.

@senivam senivam merged commit e2ee2e2 into eclipse-ee4j:master Apr 10, 2019
@rvowles
Copy link

rvowles commented May 8, 2019

Netty is still unusable because of #3500

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants