As I’m celebrating 15 years of development of the VelocityReport/Velocity Web plugin, and since I just released a new v4.0 release** on ServoyForge, I keep wondering:
Why isn’t everyone using it (that I’m aware of)?
Do people know that it is much more than a reporting tool?
That it is free to use in commercial projects Open Source under the FreeBSD license?
I have to suppose developers new to the Servoy world might not be aware of its existence or what it can do for them… For example, have you ever thought of using Servoy to build dynamic public web sites? To serve a REST API with high requests load?
I might be producing tutorials on how to better use Velocity for real world solutions if people are interested, just let me know!
** v4.0 includes refactored/cleaned-up internals, dropped support for Java < 11, reorganized zip distribution package, as well as a special “VelocityJakarta” zip release ready for Servoy 2025.09 and Tomcat 10+ - get it while it’s hot
we’ve run into a bit of an issue and wanted to get your input.
We’re currently using your velocityReport plugin (latest version) alongside JasperReports from Servoy. With the recent JasperPlugin release 7.0.4, a CVE fix was implemented which also included the removal of commons-collections.jar.
Since this update, the velocityReport plugin is no longer working on our end.
I’ve already commented on the corresponding Servoy issue, and Gabor provided some initial feedback. You can find the discussion here:
From your perspective:
Does velocityReport require an update to work without commons-collections, or would this need to be addressed on the JasperReports/Servoy side?
Any guidance on how to proceed would be greatly appreciated.
I’ll have a look.
If it’s only my code, then I can probably find a workaround, but if internal libraries used by Velocity are relying on commons-collections then I might not be able to make it work.
I’ll dig on my end and will keep you posted.
I’ve digged into that, and it looks like the Apache Velocity lib itself is referencing commons-collections.
But from the discussion on the ticket you reference, jasper itself no longer requires it, so it shouldn’t be a problem if it is present. Just keep the commons-collections jar in the /velocityreport/ folder. Just add it back if you have removed it and Velocity should work again…
