[ 
https://issues.apache.org/jira/browse/SLING-4537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14377765#comment-14377765
 ] 

Tomek Rękawek commented on SLING-4537:
--------------------------------------

Is there any other issue in the contentloader 2.1.11-SNAPSHOT that bothers you? 
I'd like to avoid reverting the SLING-4223 as I already use the extensible 
content readers, but I can help fixing all found issues ASAP.

> Provide a backwards compatible API in o.a.s.jcr.contentloader
> -------------------------------------------------------------
>
>                 Key: SLING-4537
>                 URL: https://issues.apache.org/jira/browse/SLING-4537
>             Project: Sling
>          Issue Type: Bug
>          Components: JCR
>            Reporter: Radu Cotescu
>            Assignee: Radu Cotescu
>             Fix For: JCR ContentLoader 2.2.0
>
>
> Changes proposed in SLING-3534 introduced a major API change which is not 
> really needed. Instead we should increase the API version from 0.1 to 0.2 
> (instead of 1.0.0) in order to allow upgrades of the 
> {{org.apache.sling.jcr.contentloader}} bundle independent of upgrades of the 
> {{org.apache.sling.servlets.post}}:
> {noformat}
> org.osgi.framework.BundleException: Unresolved constraint in bundle 
> org.apache.sling.jcr.jackrabbit.usermanager [55]: Unable to resolve 55.0: 
> missing requirement [55.0] osgi.wiring.package; 
> (&(osgi.wiring.package=org.apache.sling.servlets.post)(version>=2.1.0)(!(version>=3.0.0)))
>  [caused by: Unable to resolve 112.0: missing requirement [112.0] 
> osgi.wiring.package; 
> (&(osgi.wiring.package=org.apache.sling.jcr.contentloader)(version>=0.1.0)(!(version>=1.0.0)))]
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to