27

When I use the Java 8 method reference double colon operator (::) with new operator (e.g. MyType::new), I get this error in Eclipse of Spring Tool suite (STS):

The type org.eclipse.jdt.annotation.NonNull cannot be resolved. It is indirectly referenced from required .class files

How to get rid of this error?

Improve this question

4 Answers 4

Reset to default
21

Error description is provided in Stephan Herrmann's comment. There is open Eclipse issue to make this issue more user friendly.

Solution is to include following dependency:

<dependency>
    <groupId>org.eclipse.jdt</groupId>
    <artifactId>org.eclipse.jdt.annotation</artifactId>
    <version>2.0.0</version>
</dependency>
Improve this answer
Sign up to request clarification or add additional context in comments.

4 Comments

Right, the error indicates that the Eclipse project is configured to perform annotation based null analysis, but no null annotations are available on the classpath. Making null annotations available (by whichever dependency mechanism your project is using) is not just a workaround but actually the proper solution. The Eclipse bug is about suitably reporting this configuration issue (better than the resolve error in the question).
@StephanHerrmann, thanks for clarification. I updated my answer.
This guff isn't needed at runtime, so why not declare it a "provided" dependency? (Since we have to use a dependency manager to kludge this to start with)
I fully agree that this should not or rather must not(!) be fixed by fiddling with dependencies in the pom! In our code we got said error and we are nowhere using any NonNull-related eclipse annotation (nor does any code that we depend on). It seems that the simple presence of a .filter(Objects::nonNull) expression as part of a longer stream chain causes this issue and IMHO that's a clear bug!
20

Eclipse has a feature called annotation-based null analysis, which provides compile-time checks using annotations (e.g. @NonNull or @Nullable). You get this error when these annotation types are missing in the classpath.

If you don't plan to use the annotation-based null analysis feature, you can just disable it in Eclipse.

Open the global or project settings and go to Java > Compiler > Warnings. In the Null analysis category, uncheck Enable annotation-based null analysis. Then rebuild the workspace and those errors won't show again.

Improve this answer

1 Comment

This really should be the accepter answer instead of adding other dependency to the project and not even with a runtime scope.
5

I have solved it by changing the "Use default annotation for null specifications"

I have enter the both class names: 

javax.annotation.Nonnull
javax.annotation.Nullable
Improve this answer

Comments

-1

I was able to resolve this by adding a @NonNull annotation. It got underlined in red because the Eclipse annotations were not present. Hovering over the @NonNull gave me the option to "Fix Project Setup ...", and that cleared the error. Then I deleted the @NonNull.

Improve this answer

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.