Please include JSR305 into the project

Question

Please include JSR305 into the project

Opened this issue 5 years ago · 10 comments

I have Java 11 project and struggling from "split-package" issue (the first link in Google leads here). Please consider merging JSR205 (common annotations) with JSR305 to help users to avoid this problem.

You can use com.google.code.findbugs:jsr305 as reference JSR305 implementation.

Answer 1 · 2020-08-03T12:19:15.000Z

@m0mus, @lukasj, @rotty3000 and other maintainers, what do you think? Are there any discussions or plans?

Answer 2 · 2020-08-03T13:37:43.000Z

we're busy with getting EE 9 out, this will be revisited once that is done.

Answer 3 · 2021-01-08T21:07:52.000Z

@lukasj Has this been revisited?

Answer 4 · 2021-09-06T17:00:34.000Z

@lukasj Has this been revisited?

It seems they are busy again. @lukasj @jameskleeh @remal
I've seen a good PR by @michael-schnell #91 , but it seems it is huge problem to solve.

Answer 5 · 2021-09-06T17:09:04.000Z

have you seen #89 ? what else do you need and why?

Answer 6 · 2021-09-06T17:11:47.000Z

@lukasj Glad to see it! When can we expect to get a release that contains those annotations?

Answer 7 · 2021-09-06T17:21:08.000Z

I'm not the right person to answer that. For general schedule, see https://eclipse-ee4j.github.io/jakartaee-platform/jakartaee10/JakartaEE10#jakarta-ee-10-schedule

Answer 8 · 2021-09-10T14:40:37.000Z

Anyone to review #91 ?

Answer 9 · 2021-10-26T16:39:09.000Z

#91 just got closed as WON'T FIX but as mentioned plenty of people need this functionality. So what's the plan? Will someone reimplement the annotations from scratch (ideally with the same class names as IDEs depend on them)?

Answer 10 · 2021-10-27T08:14:34.000Z

As far as I understand it, there are license issues and the author from Google doesn't want to help. The only option is to reimplement these annotations. Feel free to do it and introduce a PR.