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

HttpServer artifact in addition to Jetty #434

Open
ericraskin opened this issue Feb 18, 2020 · 0 comments
Open

HttpServer artifact in addition to Jetty #434

ericraskin opened this issue Feb 18, 2020 · 0 comments
Labels
type: process A process-related concern. May include testing, release, or the like.

Comments

@ericraskin
Copy link
Contributor

What the problem is:

As reported in #397, the 8.2 version of Jetty included in the google-oauth-client-jetty artifact is incompatible with newer versions of Jetty. Proposed upgrades to Jetty 9.4 require evaluation. It was suggested that an HttpServer implementation might be better than upgrading Jetty.

Describe the solution you'd like
I would like a new artifact google-oauth-client-httpserver created. I have already written the code, but it is currently under the jetty artifact, which causes confusion.

Describe alternatives you've considered
Upgrading Jetty to 9.4 is under consideration, but both options may be the best solution (upgrade Jetty AND implement an HttpServer version).

@yoshi-automation yoshi-automation added the triage me I really want to be triaged. label Feb 19, 2020
@chingor13 chingor13 added the type: process A process-related concern. May include testing, release, or the like. label Feb 21, 2020
@yoshi-automation yoshi-automation removed the triage me I really want to be triaged. label Feb 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: process A process-related concern. May include testing, release, or the like.
Projects
None yet
Development

No branches or pull requests

3 participants