Hi devs, I finally started the long waiting refactoring to deal with conflicting ScriptContext and VelocityContext. * they are now fully in sync (at least that's the goal when you use them properly :)) * VelocityContext moved to a more internal thing or at least very specific (use case where you execute yourself some Velocity code). In general if you want to set or access script bindings, do it trough ScriptContext. * new ScriptContextManager#getCurrentScriptContext which directly return a not updated ScriptContext. To be used when you want to set binding mostly and you don't care if it's up to date or not. If there is any chance you access anything in the script context it's safer to use #getScriptContext So if you have weird behavior with Velocity variable you know who to blame. Please report me anything that looks wrong on this area. -- Thomas Mortagne