Closed io7m closed 8 years ago
It's seems that you additionally need com.google.code.findbugs:annotations package
<dependency>
<groupId>com.google.code.findbugs</groupId>
<artifactId>annotations</artifactId>
<version>2.0.3</version> <!-- Any version should work -->
</dependency>
We may need to add an option not to use additional annotations... You can add missing dependency as a workaround for now.
Do the annotations appear in the generated code? If so, it might be preferable to add an option to specify which @Nonnull
class to use, as there are many competing standards.
Yes, It's currently not configurable. There should be some kind of
enum NonnullAnnotaionFlavour {
NONE,
FINDBUGS_ANNOTATIONS,
CHECKERFRAMEWORK,
// ...
}
Would it be possible to simply specify a fully-qualified name of an annotation?
I've released 3.0-rc1 version. javax.annotation.Nullable, javax.annotation.Nonnull and javax.annotation.ParametersAreNonnullByDefault are used only if these classes are present in classpath during compilation
When using the shaded artifact in a project with no other dependencies, the code generator says:
An example project here reproduces it:
https://github.com/io7m/adt4j_test