Hi List, 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 configuration helper service lifecycle) using the configuration artifact's url as the key. As a result checks on "needsNewVersion"will typically result in false.
Smells like a bug unless this is not an intended use case? Thus my question is what the idea on configuration artifact lifecycle is as they have no versioning like bundles. Furthermore, please note that the cache implementation is a threat to memory resources as no weak references are being used. Regards, Bram
