untying the javax->jakarta knot, anyone?

Hello all,
 
VelocityTools (VelocityViewServlet and friends) reference Servlet API and that was stripped of any "Java" label not to violate Oracle's trademark (https://www.theserverside.com/blog/Coffee-Talk-Java-News-Stories-and-Opinions/Re-introducing-Jakarta-EE-Eclipse-takes-Java-EE-back-to-its-roots)
the package change was introduced with Jakarta Servlet 5.0 from October 2020 (https://en.wikipedia.org/wiki/Jakarta_Servlet)
Velocity-tools however is still stuck in servlet APi 3.1 (from May 2013) (https://velocity.apache.org/tools/3.1/changes.html)
 
3 years without action is too long. Somehow, this change must be addressed. Not doing anything would indicate to users that velocity is dead and users would look for other solutions.
So, what could be done?
 
I personally like "the log4j2 solution": two separate maven artefacts, user chooses if he wants "this or that" package name (see https://logging.apache.org/log4j/2.x/manual/webapp.html)
IDK how they build it (switch package names in source code? clone code?) but maybe the same approach could be used for VelocityTools?
 
I could even imagine to leave old servlet API totally behind. Whoever needs old servlet stays on tools 3.1 (or, if any bugfix, 3.1.1), others move on.
 
Any opinions?
cheers,
Gernot