Add an errorprone check and typed annotation for Javax -> Jakarta

[mglazer]

Before this PR

Legacy javax.ws.rs types could be submitted to methods which only accept jakarta.ws.rs types at runtime.

After this PR

==COMMIT_MSG==
Add an errorprone check and typed annotation for Javax -> Jakarta

There is a certain class of very problematic cases whereby if you have
a method such as the following:

myJerseyResource.register(/* this is of type Object */ object);

Then if you supply a resource which includes any javax.ws.rs
annotations on it, then those will not be registered if your Jersey
version is 3.x or later (and you'll only find this out at runtime).

The opposite is also true if you try to supply resources annotated
with jakarta.ws.rs to Jersey 2.x.

To address this, this commit attempts to add an errorprone check
which lets implementors add an annotation @ForbidJavax to methods
which have been knowingly migrated to Jakarta EE9 and cannot
accept legacy javax types.
==COMMIT_MSG==

Possible downsides?

[changelog-app]

Generate changelog in changelog/@unreleased

Type

• Feature
• Improvement
• Fix
• Break
• Deprecation
• Manual task
• Migration

Description

Add an errorprone check and typed annotation for Javax -> Jakarta

There is a certain class of very problematic cases whereby if you have
a method such as the following:

myJerseyResource.register(/* this is of type Object */ object);

Then if you supply a resource which includes any javax.ws.rs
annotations on it, then those will not be registered if your Jersey
version is 3.x or later (and you'll only find this out at runtime).

The opposite is also true if you try to supply resources annotated
with jakarta.ws.rs to Jersey 2.x.

To address this, this commit attempts to add an errorprone check
which lets implementors add an annotation @ForbidJavax to methods
which have been knowingly migrated to Jakarta EE9 and cannot
accept legacy javax types.

Check the box to generate changelog(s)

• Generate changelog entry

[mglazer]

When the CJR change goes through it should also resolve the error that I'm currently getting where I'm not publishing the annotations correctly somehow.

[mglazer]

Added a couple of more tests, one to handle the case where you're supplying a resource which extends from a JaxRS annotated interface, and another to assert that this errorprone check is not perfect, and can't handle the case where there is no type information at all on the ingress types.

[carterkozak]

Thanks!

[mglazer]

👍