Eclipse @NonNull annotations with Maven and Jenkins

Question

I would like to use the new @NonNull annotation from Eclipse Juno but the project I'm working on is based on Maven and is deployed with Jenkins.

Is there any way that my annotations won't break the code for other developers who don't use Eclipse and for Jenkins?

P.S.: Null-checking of method parameters does not even work with Eclipse and the Maven plugin (the Maven plugin compiles without problems but there is no error thrown when a method gets called with a null parameter even if annotated by @NonNull).

P.S.: Seeinng that my thread is a few months old, has anything better surfaced to get NonNull annotations with Maven?

Is this about pure Java development or Eclipse plugin development? In the plugin case, using Tycho would be sufficient. — Bananeweizen, Jul 31 '12 at 19:34
http://stackoverflow.com/questions/13291713/force-maven-to-fail-the-build-on-nonnull-violations — alexbt, Feb 19 '17 at 13:56
https://sling.apache.org/documentation/development/jsr-305.html — alexbt, Feb 19 '17 at 14:00

Ajay George · Accepted Answer · 2012-07-31T18:23:04.770

2

There is a Eclipse Bug raised to track publishing these annotations on to Maven Central.

The only work around I see for now is manually downloading the jar and then publishing it to your internal Maven repo.

UPDATE: To use it in maven builds consider using Eclipse JDT instead of javac. This could help.

edited Jul 31 '12 at 18:23

answered Jul 31 '12 at 15:59

Ajay George

11,759
1
40
48

Thanks! This will prevents compile errors for the others. But how can I get Maven to perform the null checks? – Konrad Höffner Jul 31 '12 at 16:01
2

If I am not wrong these annotations will be specific to Eclipse JDT. So you need to configure Maven to use JDT instead of javac – Ajay George Jul 31 '12 at 16:09
I don't want to change the compiler of this big project but in my own ones I will certainly do this, thanks! – Konrad Höffner Aug 01 '12 at 09:40

Eclipse @NonNull annotations with Maven and Jenkins

1 Answers1