[YANGTOOLS-907] Get rid of javax.annotation nullness annotations Created: 03/Oct/18 Updated: 25/Mar/19 Resolved: 25/Mar/19 |
|
| Status: | Resolved |
| Project: | yangtools |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 3.0.0 |
| Type: | Improvement | Priority: | Medium |
| Reporter: | Robert Varga | Assignee: | Robert Varga |
| Resolution: | Done | Votes: | 0 |
| Labels: | java11 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Description |
|
Nullness annotations are not working with Java 11, as their retention scope is runtime, hence they force jars to import javax.annotation. Remove them in favor of JDT annotations, which have retention=class. |
| Comments |
| Comment by Robert Varga [ 05/Oct/18 ] |
|
We actually cannot sensibly do this, as it will push nullness errors to the users' IDE. A better plan is needed. |
| Comment by Robert Varga [ 09/Oct/18 ] |
|
odlparent-4.0.3 will solve the JDK11 compatibility, hence we can postpone this to later. |