Is there a way to denote nullability using javadoc? I have to ship only one jar due to enterprise madness and annotations seem to have deps as well

There has to be a way because @Nullable shows up in Spring API javadoc: https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/beans/factory/support/AbstractBeanFactory.html#evaluateBeanDefinitionString-java.lang.String-org.springframework.beans.factory.config.BeanDefinition-

@Stephan Schroeder that's because @Nullable has the @Documented annotation: https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/lang/Nullable.html

and this disqualifies it for you??

I can't have a dependency on the jar

you could simply write for each @param and @return if null is allowed.

yep

or maybe create a fat-jar that contains jsr305??

does that create collisions if they have the same dep?

if you have conflicting versions of jsr305 (is that a thing?), than yes

You do not need a hard-dependency on the annotations jar. You can include it in your build process, but your library will be usable without clients also depending on the annotations jar.

@diesieben07 as long as the annotations are on the classpath right?

No.

thanks