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.

Sign up for GitHub

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

Jump to bottom

Ensure a message is logged if we can not create an override #80

Merged
merged 2 commits into from
Jun 9, 2016
Merged

Ensure a message is logged if we can not create an override #80

merged 2 commits into from
Jun 9, 2016

Commits on Apr 11, 2016

  1. Ensure a message is logged if we can not create an override 

    If the first access of the ClassFilter is from a class being auto wired
then the root cause of the Issue can get swallowed and it is not clear in
the logs what is wrong.  So if something goes wrong always log the error
at the expense that it gets logged twice (which is not a bad thing as it
is fatal anyway and will cause Jenkins to pretty much not work at all)
    @jtnord
    jtnord committed Apr 11, 2016
    Configuration menu
    Copy the full SHA
    42c8f65 View commit details
    Browse the repository at this point in the history

Commits on Jun 9, 2016

  1. Move the loading of the pattern override into the try block

    @jtnord
    jtnord committed Jun 9, 2016
    Configuration menu
    Copy the full SHA
    7be1d81 View commit details
    Browse the repository at this point in the history