[
https://issues.apache.org/jira/browse/TAP5-2358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14047280#comment-14047280
]
Hudson commented on TAP5-2358:
------------------------------
FAILURE: Integrated in tapestry-trunk-freestyle #1264 (See
[https://builds.apache.org/job/tapestry-trunk-freestyle/1264/])
Fixes an exception caused by the implementation of TAP5-2358. (thiagohp: rev
aab59abec15d6c51321d028cb285da60ad97c2ae)
* tapestry-ioc/src/main/java/org/apache/tapestry5/ioc/internal/RegistryImpl.java
> 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)
