You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[sdk-platform-java] Logging: capture and re-throw more clear error when sfl4j not in classpath but logging enabled. #12392
For scenario where customer app does not have logging dependency (SLF4J), but turns on logging via env variable, logging would fail. Currently, this would throw ClassNotFoundException.
For better customer experience, we can capture this and re-throw with more clear error message to communicate to customer.
Note: if change, this applies to both Gax and Auth. Need code changes in both repos.
changed the title [-]Logging: capture and re-throw more clear error when sfl4j not in classpath but logging enabled.[/-][+][sdk-platform-java] Logging: capture and re-throw more clear error when sfl4j not in classpath but logging enabled.[/+]on Apr 1, 2026
Activity
[-]Logging: capture and re-throw more clear error when sfl4j not in classpath but logging enabled.[/-][+][sdk-platform-java] Logging: capture and re-throw more clear error when sfl4j not in classpath but logging enabled.[/+]