In real projects—both AEM On-Premise and AEM as a Cloud Service—deprecated warnings like Logback show up frequently.

Check your AEM SDK version and use the following URL to view the deprecated API list:

https://javadoc.io/doc/com.adobe.aem/aem-sdk-api/<AEM SDK Version>/deprecated-list.html

https://javadoc.io/doc/com.adobe.aem/aem-sdk-api/<AEM SDK Version>/deprecated-list.html

Report highlights deprecated APIs:

Three things stand out:

• _{^{ch.qos.logback}} is marked as deprecated
• It is flagged for removal
• Several APIs are unsupported in AEM as a Cloud Service

From these points, the next step is:

• Replace the library
• Upgrade dependencies
• Fix the issue immediately

Taking immediate action is often wrong. More factors matter.

Is this warning actually coming from your code — or from the platform itself?

What the Deprecation Warning Actually Means

TODO

Where Logback Is Coming From in Your Project

TODO

What You Should Fix vs What You Should Not

TODO

A Simple Checklist for AEM Developers

TODO