On Fri, Aug 08, 2014 at 04:57:41PM +0000, Jeremy Daggett wrote: > Several of us have chatted about using the antlr4 annotation processor [1] > for @Nullable [2] and @NotNull [3] as a replacement for the jclouds @Nullable > annotation [4]. The annotation we use now is essentially just a hint that > something could be null. > > This would require a additional 10k dependency on > "antlr4-annotations-4.3.jar”. How does the community feel about using these > compile time annotations for 2.0?
What problem does this solve? Generally I believe that the complexity of magical annotations discourages potential contributors more than it increases code quality, so we should have a compelling reason to take this dependency. -- Andrew Gaul http://gaul.org/
