Hi. We'll publish the 2.0 one day, it's slowly moving...
Thank you for your proposal. Of course, it is interesting for the project if you can share your 1.7 bugfixes as long as your synchronization work on the 2.0 branch.
The process is rather easy: patches are to be submitted on JIRA : https://issues.apache.org/jira/browse/VELOCITY/
Very small patches (too small to be considered intellectual property) don't need anything else. For more consequent patches, some people say you should at least add a sentence like "feel free to use this patch under the Apache License" in the issue.
Claude On 04/03/2015 17:48, Alex Fedotov wrote:
Hello Guys, We use Velocity quite a bit and are considering moving forward and deploying the trunk build in production even though there never was a 2.0 release. We currently use a custom 1.7 build with a couple of bugs fixed by us. One area where we are going to make some changes before it can go in production is the synchronization in the VelocimacroFactory and VelicimacroManager classes. It appears to be a mix of ConcurrentHashMaps and global synchronized blocks. Our code is highly threaded, loads quite a bit of templates dynamically at run-time and having these global locks would likely present a synchronization hotspot. Our plan is to see if we can cleanup the synchronization in this area keep it robust, but remove the global synchronized blocks. If you guys have any interest in accepting our contribution back please let me know what the process should be. Thank you, Alex
--------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org For additional commands, e-mail: dev-h...@velocity.apache.org
