Ran into a strange issue with the combination of a POJO decorated with Lombok annotations that included a @Deprecated field.

When the annotation includes non-default values for forRemoval or since attributes, the POJO Codec crashes with this exception:

"Read annotation interface java.lang.Deprecated for [field] already exists in [class]"

Debugging into it, the issue was that the annotation on the field did not match the annotation on the methods.  Lombok doesn't copy down the attributes into generated code and so this code fails on the equality check:

public PropertyMetadata<T> addReadAnnotation(final Annotation annotation) {
    if (readAnnotations.containsKey(annotation.annotationType())) {
        if (annotation.equals(readAnnotations.get(annotation.annotationType()))) {
            return this;
        }
        throw new CodecConfigurationException(format("Read annotation %s for '%s' already exists in %s", annotation.annotationType(),
                name, declaringClassName));
    }
    readAnnotations.put(annotation.annotationType(), annotation);
    return this;
} 

But this got me wondering, why are you grabbing all the annotations at all?  I'd expect you to only care about the ones defined in 

org.bson.codecs.pojo.annotations

Is there a reason for the driver to know about other base java, spring, jackson, etc annotations?  If not, seems like there may be some value in restricting these checks.