[
https://issues.apache.org/jira/browse/TAP5-2422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14234636#comment-14234636
]
Hudson commented on TAP5-2422:
------------------------------
SUCCESS: Integrated in tapestry-trunk-freestyle #1353 (See
[https://builds.apache.org/job/tapestry-trunk-freestyle/1353/])
TAP5-2422: Include the MappedConfiguration key in the error message for
duplicate contributions (jkemnade: rev 9b5e19035f0e779f40231b0275e473c7def1b2cc)
*
tapestry-ioc/src/main/java/org/apache/tapestry5/ioc/internal/ValidatingMappedConfigurationWrapper.java
*
tapestry-ioc/src/test/groovy/ioc/specs/ValidatingMappedConfigurationWrapperSpec.groovy
*
tapestry-ioc/src/main/resources/org/apache/tapestry5/ioc/internal/IOCStrings.properties
* tapestry-ioc/src/main/java/org/apache/tapestry5/ioc/internal/IOCMessages.java
> Improve conflicting service configuration contribution error message (mapped
> config)
> ------------------------------------------------------------------------------------
>
> Key: TAP5-2422
> URL: https://issues.apache.org/jira/browse/TAP5-2422
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-ioc
> Affects Versions: 5.4
> Reporter: Ville Virtanen
> Assignee: Jochen Kemnade
> Fix For: 5.4
>
>
> Currently the error message does not include the key that was used to
> contribute twice to mapped configuration. This would be useful when figuring
> out where the problem is.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
