eclipse-platform
Build failure correlates with new javax-annotation warning
Tycho builds now report
WARNING: Annotation classes from the 'javax.inject' or 'javax.annotation' package found. It is recommended to migrate to the corresponding replacements in the jakarta namespace. The Eclipse E4 Platform will remove support for those javax-annotations in a future release. To suppress this warning, set the VM property: -Declipse.e4.inject.javax.warning=false To disable processing of 'javax' annotations entirely, set the VM property: -Declipse.e4.inject.javax.disabled=true
The QVTo build (https://ci.eclipse.org/qvt-oml/job/qvto-master/546/console) that does not use javax.annotation fails with the apparently unrelated
org.apache.maven.surefire.util.SurefireReflectionException: java.lang.ClassNotFoundException: org.apache.maven.surefire.junit4.JUnit4Provider at org.apache.maven.surefire.util.ReflectionUtils.loadClass(ReflectionUtils.java:249)
However adding a requirement dependency for javax.annotation fixes the build.
It would appear that the warning that javax.annotation is going obsolete malfunctions when javax.annotation is not actually in use.
Is this similar to #821 ?
Possibly, but I titled this issue 'correlates' since a causality between javax.annotation and JUnit4Provider is surprising.
A similar JUnit4Provider problem is reported in https://bugs.eclipse.org/bugs/show_bug.cgi?id=582650.
There is a problem when using https://download.eclipse.org/releases/2023-12/202311171000 to provide org.eclipse.sdk.feature.group. The problem goes away when instead using https://download.eclipse.org/releases/2023-12/202310271000.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=582650#c5 identifies probably the same JUnit4Provider problem occurring between https://download.eclipse.org/releases/2023-12/202310271000 and https://download.eclipse.org/releases/2023-12/202311171000.