Frankly, I think getting rid of Anakia might be valuable, however, currently it just works, so I haven't touched it even though it is problematic. At the same time, it is build-time only dependency, so it does not impact users much.
>The 1.x branch of velocity has a security problem, which is referenced by our github repo and we should try to do something about it. Been there, asked commons devs to release commons 2.x security fix: https://lists.apache.org/thread/c92czjl95vwzgcqhkwhjb643brlf6tpm I just noticed there was an unsent email draft: https://lists.apache.org/thread/w1kk0hjtp1bl585rypzco2v6fng3wklh Sure LLMs might help a lot with rework of the docs, however, I am afraid it would still take significant time. PS. My current goal is to implement "explicitly set to empty" vs "unset" values for the UI controls. Vladimir
