Bug 415755 - [null] multiple nullable annotations
Summary: [null] multiple nullable annotations
Status: CLOSED DUPLICATE of bug 369079
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.3   Edit
Hardware: PC All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Stephan Herrmann CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-23 08:47 EDT by Marcin Wisnicki CLA
Modified: 2013-08-23 10:18 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Marcin Wisnicki CLA 2013-08-23 08:47:24 EDT 
Currently only a single annotation type per nullability category can be defined.
Since there are many competing types and Eclipse's are least popular, this configuration dialog should be extended to accept lists of types. Even better if it could handle wildcards like "*.Nullable".

Default configuration should include annotations from popular packages:

- javax.validation.constraints
- edu.umd.cs.findbugs.annotations
- javax.annotation
- com.intellij.annotations
- lombok

See also http://blog.jetbrains.com/idea/2011/03/more-flexible-and-configurable-nullublenotnull-annotations/
Comment 1 Stephan Herrmann CLA 2013-08-23 10:18:41 EDT 
We already have a request for this.
Feel free to join the discussion there.

*** This bug has been marked as a duplicate of bug 369079 ***