Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backport "Reduce log level for message re: missing annotation" [SPR-9447] #14082

spring-projects-issues opened this issue May 27, 2012 · 1 comment


Copy link

@spring-projects-issues spring-projects-issues commented May 27, 2012

Chris Beams opened SPR-9447 and commented

Affects: 3.1.1

This issue is a backport sub-task of #13871

Copy link
Collaborator Author

@spring-projects-issues spring-projects-issues commented Jun 27, 2012

Chris Beams commented

commit 7d61153821df3dc9f72ca8f70cd70b98ee7a7c6e
Author: Chris Beams <>
Commit: Chris Beams <>

    Reduce log level for message re: missing annotation
    Previously (since Spring 3.1.1) RecursiveAnnotationAttributesVisitor
    logs at level WARN when ASM parsing encounters an annotation or an (enum
    used within an annotation) that cannot be classloaded. This is not
    necessarily indicative of an error, e.g. JSR-305 annotations such as
    @Nonnull may be used only for static analysis purposes, but because
    these annotations have runtime retention, they remain present in the
    bytecode. Per section of the JLS, "An annotation that is present
    in the binary may or may not be available at run-time via the reflective
    libraries of the Java platform."
    This commit lowers the log level of these messages from warn to debug,
    but leaves at warn level other messages dealing with the ability
    reflectively read enum values from within annotations.
    Issue: SPR-9447
    Backport-Issue: SPR-9233
    Backport-Commit: f55a4a1ac5a202f00dc427ba0f94d5123ec7b2de

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant