Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse.org-architecture-council] Encourage projects to use JDT null analysis & null annotations for Neon

> Am 29.09.2015 um 10:54 schrieb Daniel Megert <daniel_megert@xxxxxxxxxx>:
> 
> > Reformulating: Since the JDT committers know their tools much better than anyone else on the planet: how much effort would it be to provide a basic tool that runs the null simulation / analysis on an > 
> > Eclipse workspace and outputs a text file with its findings? 
> > And: Can an JDT committer provide that code skeleton? 
> 
> This largely depends on how a product defines its general API rules. For Eclipse the first step would be to add @org.eclipse.jdt.annotation.NonNullByDefault to each package. Since you mentioned a bug that you filed (bug number?), I suggest we move this discussion to that bug. 

Summary changed a bit in the meanwhile but I’m referring to bug 472710: [quick assist][null] Offer add @Nullable support to method return values or parameters
https://bugs.eclipse.org/bugs/show_bug.cgi?id=472710


Just in case this is of interest:
I tried the current tooling to make the error reporting use @Nullable annotations and struggled. Mostly because the libraries I used do not have annotations and I wasn’t able to override the default behavior.  After reviewing Konstantin and my own first-time experience, I tend to believe we can start with a limited feature set first: Annotating method return values and method parameters on ‚root‘ method declarations (i.e. methods that do not override any method). 



But I agree, this needs a longer discussion which probably should take place in bugzilla. Dani, I’d use bug 472710 but maybe creating a new bug (maybe under AC) may be better?

Marcel

> 
> Dani 



Back to the top