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

Konrad Windszus updated SLING-5462:
-----------------------------------
    Attachment: SLING-5462-v01-failing-test.patch

Attached is a patch which should fix the order. Unfortunately some tests are 
breaking now
{code}
Failed tests: 
  
MockBundleContextDynamicReferncesOsgiR6Test.testAddRemoveMandatoryMultipleService:135->assertDependencies2:174
 expected:<[dependency2a]> but was:<[dependency2a, dependency2b]>
  
MockBundleContextDynamicReferncesTest.testAddRemoveMandatoryMultipleService:134->assertDependencies2:160
 expected:<[dependency2a]> but was:<[dependency2a, dependency2b]>
  MockBundleContextTest.testServiceRegistration:86 expected 
same:<org.apache.sling.testing.mock.osgi.MockServiceReference@346a65b0> was 
not:<org.apache.sling.testing.mock.osgi.MockServiceReference@84a09bec>
  OsgiContextImplTest.testRegisterMultipleServices:92 expected same:<[]> was 
not:<[]>
{code}
[[email protected]] Could you have a look at that?

> MockServiceReference sorts in the wrong way w.r.t. service ranking
> ------------------------------------------------------------------
>
>                 Key: SLING-5462
>                 URL: https://issues.apache.org/jira/browse/SLING-5462
>             Project: Sling
>          Issue Type: Bug
>          Components: Testing
>    Affects Versions: Testing OSGi Mock 2.0.0
>            Reporter: Bertrand Delacretaz
>            Priority: Minor
>         Attachments: SLING-5462-v01-failing-test.patch
>
>
> I'll add tests that demonstrate that, by comparing with the sorting done by a 
> real OSGi framework.



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

Reply via email to