The question for me is whether we should rely on the dormant standard (which did never release anything officially) 305, because that is not supported by Eclipse or whether we should use something else? Any ideas, opinions on that? What is your experience with the JSR305 javax.annotation support in major IDEs (see also http://stackoverflow.com/questions/4963300/which-notnull-java-annotation-should-i-use <http://stackoverflow.com/questions/4963300/which-notnull-java-annotation-should-i-use>)? Konrad
> On 30 Jan 2015, at 13:37, Robert Munteanu <[email protected]> wrote: > > On Fri, Jan 30, 2015 at 2:15 PM, Konrad Windszus <[email protected]> wrote: >> What about adding annotations like >> https://code.google.com/p/jsr-305/source/browse/trunk/ri/src/main/java/javax/annotation/CheckForNull.java >> >> <https://code.google.com/p/jsr-305/source/browse/trunk/ri/src/main/java/javax/annotation/CheckForNull.java> >> to the Sling API? > > +1 > > I wonder if there is a static analyser which can fail the build when > violations are found, e.g. immediately dereferencing the result of a > method which is @Nullable. > > Robert
