Failure to log with SLF4J about aws-sdk-java-v2 HOT 4 OPEN

I just realized that there is no StaticLoggerBinder in slf4j 2.0. So the problem is most likely simply that only slf4j 1.7 is supported? Is an upgrade to slf4j 2.0 on the table?

from aws-sdk-java-v2.

@janvanbesien-ngdata @akshat62

Is there a reason you need the slf4j version inside the SDK to be upgraded?

We have some concerns about 2.x backwards compatibility (#5105 (comment)), and upgrading needs a deeper investigation work. Can you upgrade it in your project?

from aws-sdk-java-v2.

Our project already uses slf4j 2.x hence we have the slf4j-api and an slf4j 2.x provider/binding/impl on the classpath. However, this provider is incompatible with the older slf4j-api inside the SDK, hence no logging from the SDK.

My jshell example demonstrates that with the slf4j-simple provider but it's the same problem for other providers.

IIUC, the lack of backwards compatibility between slf4j providers and api that you are concerned about in #5105, is exactly what I am running into. So it is annoying either way: (a) if you upgrade, customers will have to upgrade as well. (b) If you don't upgrade, customers can't upgrade either.

You can't postpone the upgrade for ever, so (a) is the only way forward IMHO.

from aws-sdk-java-v2.

We've added a task to our backlog to investigate if it's possible to upgrade to slf4j 2.x without breaking backwards compatibility.

We don't have a timeline for when the task will be prioritized. In the meantime, anyone who'd like to see this feature supported please add a 👍 to the initial description of the issue.

from aws-sdk-java-v2.