You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@tapestry.apache.org by "Thiago Henrique De Paula Figueiredo (Jira)" <ji...@apache.org> on 2020/11/26 21:43:00 UTC

[jira] [Resolved] (TAP5-2649) Configuration should have consistent ordering

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

Thiago Henrique De Paula Figueiredo resolved TAP5-2649.
-------------------------------------------------------
    Resolution: Fixed

Implementing by applying the same module sorting to unordered configuration as done to ordered ones in TAP5-2358 .

> Configuration should have consistent ordering
> ---------------------------------------------
>
>                 Key: TAP5-2649
>                 URL: https://issues.apache.org/jira/browse/TAP5-2649
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-ioc
>    Affects Versions: 5.3, 5.4
>            Reporter: Thiago Henrique De Paula Figueiredo
>            Assignee: Thiago Henrique De Paula Figueiredo
>            Priority: Major
>              Labels: month-of-tapestry
>             Fix For: 5.6.2
>
>
> Depending on the order in which module classes with contributions to the same service with (unordered) Configuration were added to the Registry, which isn't defined, the resulting list passed to the service can have different ordering. Given the same contributions, the resulting list should always be the same.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)