I haven't followed the discussion... but I think you'll find that if we bundled a different servlet extension, it would suffer from a lack of maintenance. While basically ~every java server in Google depends on Guice (and thus we're careful to keep it stable and working well), nothing would depend on this new extension. Very few servers even depend on the existing servlet extension (as we primarily use a different technology internally). Other folks are in a better position to ensure a new servlet extension exists and is maintained. If you're just looking for a fork of the servlet extension, there shouldn't be anything special about the existing one that requires co-bundling/shipping privileges. OTOH, if you're looking for a fork of core Guice itself, that's unlikely to happen.

…

On Wed, Sep 28, 2022, 5:01 PM Ben Manes ***@***.***> wrote: @sameb <https://github.com/sameb> could we get something simple and low effort to be forward compatible? Maybe a new extension, guice-jakarta-servlet, that forks the old one with the updated imports? I don't think the community is asking for much, just a little support so that we can update our http servlet engines (tomcat, jetty, etc). — Reply to this email directly, view it on GitHub <#1490 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAQLWERF56N6JEPQRRE65P3WASW4LANCNFSM4X3Y6AIA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

Uh oh!

Support for jakarta annotations #1490

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions