Configuration artifacts can not be updated due to infinite cache
----------------------------------------------------------------
Key: ACE-174
URL: https://issues.apache.org/jira/browse/ACE-174
Project: Ace
Issue Type: Bug
Affects Versions: 0.8.0
Reporter: Bram de Kruijff
updating (or even drop/create) configuration artifacts is not being propagated
to targets. This is caused by the fact that the VelocityArtifactPreprocessor
internally caches the bytes indefinitely (at least tight to the onfiguration
helper service lifecycle) using the configuration artifact's url as the key. As
a result checks on "needsNewVersion"will typically result in false.
Furthermore, please note that the cache implementation is a threat to memory
resources as no weak references are being used.
http://www.mail-archive.com/ace-dev@incubator.apache.org/msg01345.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
