I've found out that I've actually already voted for that one :)
The issue is that different IDE and offline tools provide different annotations for the same purpose. Deciding on one vs. the others is a lot of hassle in a team that uses a diverse range of source code tools.
It would be nice if IDEA users could sidestep this debate, and simply configure some annotation(s) as having @NotNull/@Nullable semantics.
Hello Taras,
No, this is not currently possible. There's plenty of JIRA requests asking
to make the annotation FQNs configurable, so feel free to vote. :)
--
Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"
Thanks Dmitry,
This is the issue that most duplicates refer to:
http://www.jetbrains.net/jira/browse/IDEABKL-4959
I've found out that I've actually already voted for that one :)
The issue is that different IDE and offline tools provide different annotations for the same purpose.
Deciding on one vs. the others is a lot of hassle in a team that uses a diverse range of source code tools.
It would be nice if IDEA users could sidestep this debate, and simply configure some annotation(s) as having @NotNull/@Nullable semantics.
Taras