JSR 305 is dead and unapproved. We shouldn't depend on it. Wrt the more general question of nullable annotations in Maven., I vote no. I've tried this on past projects, and it only works if you use it from the beginning, and enforce it with tools and tests. There's no way we're getting this into Maven now. We have far smaller cleanup tasks that haven't been done for over a decade.
If someone tries, the end result is going to be a few scattered classes annotated with @Nullable, but no actual effect because the rest of the work hasn't been done and the annotations can't be relied on. The code will be in worse shape than it was when the effort started. On Tue, Feb 11, 2025 at 4:36 AM Xeno Amess <xenoam...@gmail.com> wrote: > > as title. > during recently learning about maven and maven-resolver, sometimes I really > think it better to have nullable/notnull annotations... -- Elliotte Rusty Harold elh...@ibiblio.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
