Rishabh Daim created SLING-13430:
------------------------------------

             Summary: Add a shared SLF4J 1.7 compatibility version property
                 Key: SLING-13430
                 URL: https://issues.apache.org/jira/browse/SLING-13430
             Project: Sling
          Issue Type: Improvement
            Reporter: Rishabh Daim


The Sling parent manages SLF4J 2.x by default. Some modules still need to 
compile against SLF4J 1.7 to remain compatible with older runtime 
distributions, as illustrated by SLING-13428 and SLING-13342.

Add a shared {{slf4j.compat.version}} property set to {{1.7.36}}. Modules can 
opt in by overriding the existing property:
{code:xml}
<properties>
    <slf4j.version>${slf4j.compat.version}</slf4j.version>
</properties>
{code}

Keep SLF4J 2.x as the default. The existing dependency management must continue 
to align {{slf4j-api}} and {{slf4j-simple}} through {{slf4j.version}}. Removing 
the override restores the default once a module no longer needs compatibility.

h3. Acceptance criteria
# The parent provides {{slf4j.compat.version}} with value {{1.7.36}}.
# Consumer POMs can opt in with the property override above, including 
consumers of {{sling-bundle-parent}}.
# Both managed SLF4J artifacts resolve to 1.7.36 for opted-in consumers; 
consumers without the override retain 2.0.17.
# Explain the opt-in next to the property in the parent POM.

Module migrations and runtime logging-provider changes are outside this issue.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to