The alternatives would be to a) make the import optional or to b) provide a bundle that exports the javax.annotation package.
Granted a) would need a release of all bundles just like switching - so in that case I agree we are better of to just switch to the jetbrains annotations. However, I wanted to point out option b). IIRC, there is nothing preventing us to just provide the package ourselves and then it would be problem solved, no? regards, Karl On Thursday, August 2, 2018, Julian Reschke <[email protected]> wrote: > On 2018-08-02 10:55, Stefan Seifert wrote: > >> ... >> benefits: >> - removes a blocker from achieving Java 9 compatibility >> > > AFAICT, it's only Java 11 where there's an actual compat problem (but yes, > that'll be the version we need to support soonish). > > ... > drawbacks: >> - the jetbrains annotations include some more (mostly IntelliJ-specific) >> annotations than only the nullable annotations >> - the jetbrains annotations are no "standard annotations" >> ... >> > > Well, if there were "standard annotations" for this, we'd use them :-) > > > ... > > Best regards, Julian > -- Karl Pauls [email protected]
