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:
<br>myJerseyResource.register(/* this is of type Object */ object);<br>
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.
excavator is a bot for automating changes across repositories.
Changes produced by the roomba/latest-baseline-oss check.
Release Notes
4.154.0
4.155.0
Automated release, no documented user facing changes
4.156.0
4.157.0
junit-reportsplugin.4.158.0
checkUnusedDependenciestasks added bybaseline-exact-dependenciescompatible with Gradle's configure-on-demand feature.4.159.0
There is a certain class of very problematic cases whereby if you have
a method such as the following:
<br>myJerseyResource.register(/* this is of type Object */ object);<br>Then if you supply a resource which includes any
javax.ws.rsannotations 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.rsto Jersey 2.x.To address this, this commit attempts to add an errorprone check
which lets implementors add an annotation
@ForbidJavaxto methodswhich have been knowingly migrated to Jakarta EE9 and cannot
accept legacy javax types.
4.160.0
4.161.0
To enable or disable this check, please contact the maintainers of Excavator.