You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2020/11/26 21:35:00 UTC

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

    [ https://issues.apache.org/jira/browse/TAP5-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17239430#comment-17239430 ] 

ASF subversion and git services commented on TAP5-2649:
-------------------------------------------------------

Commit a2460d3b9a4de7a2b506881bbf5cc028988578e2 in tapestry-5's branch refs/heads/5.6.x from Thiago H. de Paula Figueiredo
[ https://gitbox.apache.org/repos/asf?p=tapestry-5.git;h=a2460d3 ]

TAP5-2649: Configuration should have consistent ordering

> 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)