Timeline for IDE independent @Nullable annotation
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 25, 2022 at 13:35 | history | edited | gillesB | CC BY-SA 4.0 | deleted 42 characters in body |
| Nov 25, 2022 at 13:34 | comment | added | gillesB | This is what I meant with "If javax.annotation.CheckForNull or javax.annotation.Nullable should be used is probably debatable." I think that javax.annotation.CheckForNull equals org.eclipse.jdt.annotation.Nullable according to their respective Javadoc. javax.annotation.Nullable is (according to it's Javadoc) only a hint for the developer. Till now I have not yet considered comparing the bytecode, as I added the annotations only in the compile-scope. But it is an interesting point. | |
| Nov 25, 2022 at 12:59 | comment | added | howlger | According to your screenshot you configured the wrong annotation: first has to be javax.annotation.Nullable. Please note, as far as I known, only the org.eclipse.jdt null annotations do not pollute the bytecode. | |
| Nov 25, 2022 at 11:11 | history | edited | gillesB | CC BY-SA 4.0 | added 296 characters in body |
| Nov 25, 2022 at 10:38 | comment | added | gillesB | The answer does not need the ugly import of spring-core any more. | |
| Nov 25, 2022 at 10:35 | history | edited | gillesB | CC BY-SA 4.0 | added 292 characters in body |
| Nov 25, 2022 at 10:19 | history | edited | gillesB | CC BY-SA 4.0 | added 55 characters in body |
| Nov 25, 2022 at 9:51 | history | answered | gillesB | CC BY-SA 4.0 |