[jira] [Commented] (TAP5-2358) OrderedConfiguration should have consistent ordering
[ https://issues.apache.org/jira/browse/TAP5-2358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14047275#comment-14047275 ] Thiago H. de Paula Figueiredo commented on TAP5-2358: - https://git-wip-us.apache.org/repos/asf?p=tapestry-5.git;a=commit;h=a2fac6be8bed9c9406c601409ea4c063a91a832a OrderedConfiguration should have consistent ordering Key: TAP5-2358 URL: https://issues.apache.org/jira/browse/TAP5-2358 Project: Tapestry 5 Issue Type: Improvement Components: tapestry-ioc Affects Versions: 5.3, 5.4 Reporter: Thiago H. de Paula Figueiredo Assignee: Thiago H. de Paula Figueiredo Labels: month-of-tapestry Depending on the order in which module classes with contributions to the same service with OrderedConfiguration 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 (v6.2#6252)
[jira] [Commented] (TAP5-2358) OrderedConfiguration should have consistent ordering
[ https://issues.apache.org/jira/browse/TAP5-2358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14047277#comment-14047277 ] ASF subversion and git services commented on TAP5-2358: --- Commit aab59abec15d6c51321d028cb285da60ad97c2ae in tapestry-5's branch refs/heads/master from [~thiagohp] [ https://git-wip-us.apache.org/repos/asf?p=tapestry-5.git;h=aab59ab ] Fixes an exception caused by the implementation of TAP5-2358. OrderedConfiguration should have consistent ordering Key: TAP5-2358 URL: https://issues.apache.org/jira/browse/TAP5-2358 Project: Tapestry 5 Issue Type: Improvement Components: tapestry-ioc Affects Versions: 5.3, 5.4 Reporter: Thiago H. de Paula Figueiredo Assignee: Thiago H. de Paula Figueiredo Labels: month-of-tapestry Fix For: 5.4 Depending on the order in which module classes with contributions to the same service with OrderedConfiguration 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 (v6.2#6252)
[jira] [Commented] (TAP5-2358) OrderedConfiguration should have consistent ordering
[ https://issues.apache.org/jira/browse/TAP5-2358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14047279#comment-14047279 ] ASF subversion and git services commented on TAP5-2358: --- Commit d2ccbe2dfe863ac3d136aa522758de46ff2815e6 in tapestry-5's branch refs/heads/master from [~thiagohp] [ https://git-wip-us.apache.org/repos/asf?p=tapestry-5.git;h=d2ccbe2 ] TAP5-2358 : removing some debbuging code. OrderedConfiguration should have consistent ordering Key: TAP5-2358 URL: https://issues.apache.org/jira/browse/TAP5-2358 Project: Tapestry 5 Issue Type: Improvement Components: tapestry-ioc Affects Versions: 5.3, 5.4 Reporter: Thiago H. de Paula Figueiredo Assignee: Thiago H. de Paula Figueiredo Labels: month-of-tapestry Fix For: 5.4 Depending on the order in which module classes with contributions to the same service with OrderedConfiguration 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 (v6.2#6252)
