Am 2023-03-22 um 11:24 schrieb Claude Brisson:
And it should be better to first push out a release of the engine (there is at least one CVE on the jdom dependency).
+1
Ah, and follow the movement and make the javax => jakarta migration, shouldn't we? Then, how? Does it imply a major version change? If yes, it means two releases per module...
I wouldn't waste a single minute for that unless there is a strong reason and user complaints. Only the servlet views and request/session-related stuff is affected.
PS - read somewhere on twitter: "I wish to know how many man-years the whole #Java developers community wasted on the idiotic javax -> jakarta migration so far, and more important I wish there could be a way to make @Oracle to pay for it."
I absolutely second this position. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org For additional commands, e-mail: dev-h...@velocity.apache.org
