[
https://issues.apache.org/jira/browse/SLING-3634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14077671#comment-14077671
]
Artyom Stetsenko commented on SLING-3634:
-----------------------------------------
Didn't notice the note about this in the Sling documentation. I agree that the
approach indicated there works. But I fail to see why it would be a problem to
increase the API version in the parent, given that {{Import-Package}} in each
bundle is maintained so that the version range is wide enough.
Here is a quote from http://www.slf4j.org/codes.html#version_mismatch:
{quote}
>From the client's perspective all versions of slf4j-api are compatible. Client
>code compiled with slf4j-api-N.jar will run perfectly fine with
>slf4j-api-M.jar for any N and M. You only need to ensure that the version of
>your binding matches that of the slf4j-api.jar.
{quote}
If I understand correctly, that means that a bundle compiled with any slf4j-api
should be runnable on a system providing any slf4j-api, which justifies the
version bump in the parent.
Also, doesn't this mean that {{Import-Package}} of {{org.slf4j}} may be set
globally to a value like {{[1.5,2)}} (or even any version) in the parent
instead of individually in each bundle?
> Update Parent to latest slf4j
> -----------------------------
>
> Key: SLING-3634
> URL: https://issues.apache.org/jira/browse/SLING-3634
> Project: Sling
> Issue Type: Improvement
> Components: General
> Affects Versions: Parent 19
> Reporter: Artyom Stetsenko
> Priority: Minor
>
> The currently specified slf4j 1.5.2 is nearly six years old.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
