Unfortunately javax.annotation package-uses issues have returned
<https://bugs.eclipse.org/bugs/show_bug.cgi?id=566085> :(
The effort to replace the no-longer maintained Spotify Docker
<https://bugs.eclipse.org/bugs/show_bug.cgi?id=558284>
<https://bugs.eclipse.org/bugs/show_bug.cgi?id=558284>Client
<https://bugs.eclipse.org/bugs/show_bug.cgi?id=558284> (bug 558284)
<https://bugs.eclipse.org/bugs/show_bug.cgi?id=558284> introduced a new version
of the javax.annotation bundle into Orbit
<https://git.eclipse.org/r/c/orbit/orbit-recipes/+/161789> based on Jakarta
EE’s somewhat recently released javax.annotation bundle with version 1.3.5
<https://search.maven.org/artifact/jakarta.annotation/jakarta.annotation-api/1.3.5/jar>.
This bundle doesn’t use the same approach used for the javax.annotation 1.2.0
bundle <https://bugs.eclipse.org/bugs/show_bug.cgi?id=462686#c27> to use
import-what-you-export and requiring system.bundle.
The issue only occurs on Java 8 and has been seen in the wild
<https://github.com/GoogleCloudPlatform/google-cloud-eclipse/issues/3623>. I
suspect it has not been more widespread due to increased adoption of Java 11.
I’ve pushed up a fix to the javax.annotation 1.3.5 bundle
<https://git.eclipse.org/r/c/orbit/orbit-recipes/+/167718>. I think the risk
is small, but given that we’re in RC season, it would be good to get some more
eyes on this.
If you have concerns, please comment on Bug 566085
<https://bugs.eclipse.org/bugs/show_bug.cgi?id=566085>.
Brian.
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
