You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Stefan Seifert (JIRA)" <ji...@apache.org> on 2016/07/18 16:49:20 UTC

[jira] [Resolved] (SLING-5865) Models Impl: Update to org.apache.sling.commons.osgi 2.4.0

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

Stefan Seifert resolved SLING-5865.
-----------------------------------
    Resolution: Fixed

Completed: At revision: 1753268  


> Models Impl: Update to org.apache.sling.commons.osgi 2.4.0
> ----------------------------------------------------------
>
>                 Key: SLING-5865
>                 URL: https://issues.apache.org/jira/browse/SLING-5865
>             Project: Sling
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: Sling Models Impl 1.2.8
>            Reporter: Stefan Seifert
>            Assignee: Stefan Seifert
>            Priority: Minor
>              Labels: models
>             Fix For: Sling Models Impl 1.2.10
>
>
> currently an older org.apache.sling.commons.osgi is included not featuring the latest signature changes to ServiceUtil from SLING-5041. this class is also used in sling-mock and osgi-mock based unit tests.
> the models impl bundle includes the ServiceUtil class in its bundle instead of creating a runtime dependency to it. this creates problem when running unit tests within an IDE or command line because there the OSGi classpath isolation does not take place and the tests may fail with method signature errors.
> to avoid this on future releases we should update to the latest org.apache.sling.commons.osgi 2.4.0.
> workaround for the existing releases is to control the dependency order for the unittest and ensure that org.apache.sling.commons.osgi comes first.



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