[
https://issues.apache.org/jira/browse/SLING-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14106749#comment-14106749
]
Carsten Ziegeler commented on SLING-2816:
-----------------------------------------
Actually the test is wrong and the code is right :)
The test is using the same id for the different resources which means it does
not provide three different resources, but the same resource three times with
different contents. In that case, priority does of course not play a role
> ConfigPrioritiesTest does not behave as expected
> ------------------------------------------------
>
> Key: SLING-2816
> URL: https://issues.apache.org/jira/browse/SLING-2816
> Project: Sling
> Issue Type: Bug
> Components: Installer
> Reporter: Bertrand Delacretaz
> Assignee: Carsten Ziegeler
> Priority: Minor
> Fix For: Installer Core 3.5.4
>
>
> The ConfigPrioritiesTest in installer/it does not behave as I'd expect it,
> I'll add TODOs to explain the details.
> It probably hasn't been run in a long time, as before my SLING-2815 changes
> the @Test annotation was missing, and the version of JUnit used then didn't
> complain.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
