You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2012/05/18 19:27:06 UTC

[jira] [Resolved] (SLING-2488) Update jcr.api dependency

     [ https://issues.apache.org/jira/browse/SLING-2488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Meschberger resolved SLING-2488.
--------------------------------------

       Resolution: Fixed
    Fix Version/s: JUnit Scriptable Tests Provider 1.0.8

Fixed in Rev. 1340178
                
> Update jcr.api dependency
> -------------------------
>
>                 Key: SLING-2488
>                 URL: https://issues.apache.org/jira/browse/SLING-2488
>             Project: Sling
>          Issue Type: Improvement
>          Components: Testing
>    Affects Versions: JUnit Scriptable Tests Provider 1.0.6
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: JUnit Scriptable Tests Provider 1.0.8
>
>
> The bundle depends on the old o.a.s.jcr.api 2.0.2-incubator bundle which exports the JCR API at version 1.0. With the update to the latest bundle plugin this export now causes the JUnit Scriptable Tests Provider bundle to import JCR API at (1.0,2.0] which of course does not work.
> Updating the dependency to 2.0.4 and adding JCR as an explicit dependency (inheriting the version number from dependency management) works.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira