Using @NotNull in a project where both IntelliJ and Eclipse developers are working
Posted
by
Gugussee
on Stack Overflow
See other posts from Stack Overflow
or by Gugussee
Published on 2011-01-07T14:30:58Z
Indexed on
2011/01/07
14:53 UTC
Read the original article
Hit count: 267
A co-worker on IntelliJ IDEA (working on another project) showed me the amazing @NotNull annotation. I've read messages here on SO about how starting to add @NotNull everywhere saved lots of time and headaches (and IntelliJ 10 can even add automatically @NotNull to old code when it detects that null would break havoc).
Since I read my first "Probable @NotNull violation" message (in real-time, in the IDE, even on a partial .java file that doesn't compile yet) my jaw dropped and I got hooked.
So I was wondering: is there anything that needs to be known if we want to start using @NotNull in a project where developers are using both Eclipse and IntelliJ?
I know IntelliJ ships with the annotations.jar. Is this compatible with Eclipse?
© Stack Overflow or respective owner