In KC we have had several issues where properties are being set/updated/removed? and and it would be nice to have some logging (in the JaxbConfigImpl) to figure where this is coming from. For example: is the update(override) coming from a file, a call to putProperty. What is the calling code which is setting this property.
Right now, in order to figure this out we have had to debug our application. It is pretty critical to be able to diagnose these issues w/o the need for a debugger especially in environments where debugging isn't easy (like our deployed environments).
Here is an example of one issue that we ran into.
We were correctly setting the environment property to cnv in a config file which was correctly parsed/resolved. We failed to set the environment property in Spring for the RiceConfigurer. When the RiceConfigurer loaded up it reset the environment property to the default dev. The only way to figure this out was through debugging.
There used to be some override logging statements but they were removed during a refactor. Adding back statements like this is probably a step in the right direction.