Remove overloads of NonNullUtils#checkNotNull()
authorAlexandre Montplaisir <alexmonthy@efficios.com>
Tue, 24 Nov 2015 23:51:18 +0000 (18:51 -0500)
committerAlexandre Montplaisir <alexmonthy@efficios.com>
Sun, 29 Nov 2015 03:56:21 +0000 (22:56 -0500)
commitc66ca500716a3a549b31befaa286d17371f1a0f8
tree8642396b45f93a118bbeeeda0904b1c1ab8db7c5
parent728810b6fbbe0814e96549b3c18062ba555ae31a
Remove overloads of NonNullUtils#checkNotNull()

New errors have cropped up with the latest integration build. It seems
JDT is now stricter with regards to annotated generic types vs.
un-annotated ones (where before un-annotated was similar to @Nullable,
now we don't we away with it that easily).

Variants of checkNotNull() method that used to help the compiler now
seem to do more harm than good. Just deferring to the basic "T" one
fixes the new errors. Perhaps this should have been the ideal approach
all along?

Change-Id: If998d5554b5d85ac785d21365dfeeae5d6a48bb8
Signed-off-by: Alexandre Montplaisir <alexmonthy@efficios.com>
Reviewed-on: https://git.eclipse.org/r/60650
Reviewed-by: Hudson CI
common/org.eclipse.tracecompass.common.core/src/org/eclipse/tracecompass/common/core/NonNullUtils.java
statesystem/org.eclipse.tracecompass.segmentstore.core/src/org/eclipse/tracecompass/segmentstore/core/treemap/TreeMapStore.java
This page took 0.026339 seconds and 5 git commands to generate.