On 2024/01/10 10:15:27 Gernot Hueller wrote:
> 
> 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?

We are short in committers, that's a fact. It is more or less Claude and me, 
effectively.

> 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?

This is my preference as well, two modules. Maybe a common module as a dep to 
avoid duplication, but that can be only decided after an evaluation.

> 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.

Me not because javax namespace will live for many for many years for a lot of 
reasons. I don't see a reason not to support it. As Mark Thomas said: Tomcat 
9.x will be supported for as long as there is demand for it and likely other 
Servlet containers.

Are you interesting to work on this, if yes? What would be your plan? I'd be 
willing to discuss your idea and review it.

M

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org
For additional commands, e-mail: dev-h...@velocity.apache.org

Reply via email to