[
https://issues.apache.org/jira/browse/SLING-7193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert resolved SLING-7193.
-----------------------------------
Resolution: Fixed
Fix Version/s: Testing OSGi Mock 2.3.4
Testing OSGi Mock 1.9.8
Completed: At revision: 1811972 (2.x)
Completed: At revision: 1811983 (1.x)
> osgi-mock: MockServiceReferences.compareTo reverses ordering
> ------------------------------------------------------------
>
> Key: SLING-7193
> URL: https://issues.apache.org/jira/browse/SLING-7193
> Project: Sling
> Issue Type: Bug
> Components: Testing
> Affects Versions: Testing OSGi Mock 1.9.6, Testing OSGi Mock 2.3.2
> Reporter: Stefan Seifert
> Assignee: Stefan Seifert
> Labels: mocks
> Fix For: Testing OSGi Mock 1.9.8, Testing OSGi Mock 2.3.4
>
>
> according to specification the compareTo method of the OSGi Framework
> ServiceReference implementation should implement an ascending ordering, with
> lowest ranking/highest service id first.
> in osgi-mock this is contrary - highest ranking/lowest service id first. this
> has no effect on the MockBundleContext.getServiceReference method - this
> correctly returns the service with the highest ranking/lowest service id.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
