Hi
I'm migrating from Buckminster where I was forced to use both an
old JDT (on Hudson) and current JDT interactively. My code has no
errors on either.
Using Tycho 0.26.0 I get two errors about unsafe nulls; well I
can probably workaround 2.
Using Tycho 1.0.0 I get over a thousand errors. It appears that
my custom Java annotations correcting the not-designed-for null on
List<T>.get are being ignored. e.g.
[INFO] Compiling 1035 source files to
E:\GIT\org.eclipse.ocl\plugins\org.eclipse.ocl.pivot\target\classes
[WARNING]
E:\GIT\org.eclipse.ocl\plugins\org.eclipse.ocl.pivot\src\org\eclipse\ocl\pivot\internal\manager\FlowAnalysis.java:[97]
OCLExpression asExpression =
toBeDeduced.get(alreadyDeducedIndex++);
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Unsafe interpretation of method return type as '@NonNull'
based on the receiver type '@NonNull List<@NonNull
OCLExpression>'. Type 'List<E>' doesn't seem to be
designed with null type annotations in mind
[WARNING]
E:\GIT\org.eclipse.ocl\plugins\org.eclipse.ocl.pivot\src\org\eclipse\ocl\pivot\internal\manager\FlowAnalysis.java:[356]
OCLExpression pathElement = callPath.get(pathIndex++);
^^^^^^^^^^^^^^^^^^^^^^^^^
Unsafe interpretation of method return type as '@NonNull'
based on the receiver type '@NonNull List<@NonNull
OCLExpression>'. Type 'List<E>' doesn't seem to be
designed with null type annotations in mind
What is the underlying JDT in 0.26.0 / 1.0.0?
Is it controllable?
Is there some configuration magic for Java annotation paths?
Is there a problem with the "annotations" folder being
differently special for Java / Maven ?
Regards
Ed Willink
