Remove proprietary annotations about email-rfc2822-validator HOT 2 CLOSED

It seems you misunderstood how annotation dependencies work.

First, these transitive dependencies are not needed and indeed are set to provided. If you omit them completely, this causes no issues, because the JVM was designed to allow for missing annotation classes.

Second, these nullability annotation libraries don't have "lots of others stuff is coming along", as you can see in a Maven analyses:

Not only are there no nested transitive dependencies, these are set to provided, so they are not needed at all. If you don't include them, the only thing you accomplish is that your IDE/build tool can't do proper null-checks anymore, so you basically harm your own project.

Third, these libraries are the defacto industry standard. Many many projects uses them (including popular projects such as Google Guava); either the old spotbugs version, the findbugs successor or Google's CheckerQual etc. They allow analyser tools (Spotbugs, IntelliJ etc)., to perform static analyses for nullabillity-problems. But if you don't want them, you can and that's totally fine.

from email-rfc2822-validator.

Mhm indeed didn't know that missing annotations would be ignored. Fine. But I disagree with your statement that Intellij' annotation are a defacto industry standard (findbugs/spotbugs might be). You can compare my thread "Which nonnull annotation to use" https://stackoverflow.com/questions/35892063/which-nonnull-java-annotation-to-use

from email-rfc2822-validator.