[
https://issues.apache.org/jira/browse/TAMAYA-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15884695#comment-15884695
]
ASF subversion and git services commented on TAMAYA-243:
--------------------------------------------------------
Commit dd22364a9f16b2a0c3e68f43a4c1bacd5ad89423 in
incubator-tamaya-extensions's branch refs/heads/master from [~o.b.fischer]
[
https://git-wip-us.apache.org/repos/asf?p=incubator-tamaya-extensions.git;h=dd22364
]
[TAMAYA-243] Commited the actual change to the DefaultConfigChangeObserver.
Messed up somehow the last commit.
> Change event does not contain the new value for a key after changing its value
> ------------------------------------------------------------------------------
>
> Key: TAMAYA-243
> URL: https://issues.apache.org/jira/browse/TAMAYA-243
> Project: Tamaya
> Issue Type: Bug
> Reporter: Oliver B. Fischer
> Assignee: Oliver B. Fischer
> Fix For: 0.3-incubating
>
>
> Events for a changed value of a key does not contain the new value. Only the
> value of the old value seems to be correctly updated. The crazy thing is that
> the before the last {{git pull -r}} it was the other way around.
> Unfortunately all tests are passing. This indicates a bad test coverage.
> To reproduce this bug please checkout {{767bc1e}} of the extensions and run
> the events example ({{extensions/examples/04-events-example}}).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
