Support for jakarta annotations

Do you have any time estimations for supporting jakarta.* annotations? We want to migrate to Jersey 3 but it’s impossible because GuiceFilter implements javax.servlet.Filter. Another problem is #1383.

[kashike]

#1383

[sameb]

Ugh, what a horrible mess. Silly IBM.

The proposed pull request is both invasive (on the core guice side), and a huge pit of code duplication (on the servlet extension side).

For servlet, I honestly think the best outcome is for someone else to create and host it. I’d be happy to point to it from any “official” docs. But us bundling it seems like a bad idea. The existing servlet extension already has bugs, and we don’t really maintain it except for keeping it compiling. Someone could probably fork it and make it much better already. I’m loathe to copy/paste and search/replace a large swathe of code, especially when it will have zero ongoing usages that we can validate.

As for the annotation/provider support… it adds a bunch of SPI classes and API methods. It’s not all that appealing.

@mcculls – what are y’all doing with Maven? Is this impacting you?

Let me talk to a few folks internally and see what the deal is. I imagine this impacts Dagger too?

What a gross situation.