I religiously use @NonNull annotations to mark parameters that should not be null. I was wondering if people have felt enough need for a semantical @NonEmpty annotation.
The main motivation being that for Strings usually @NonNull is not good enough because strings usually come from property files/configs or from external systems (json/yaml/whatever) and they often end up as blanks or " ".
You can argue the same goes with collections usually nulls are difficult to handle and hence empty collections are passed. I believe this annotation will make sure it covers these scenarios as I am always checking them otherwise.