And it should be better to first push out a release of the engine (there
is at least one CVE on the jdom dependency).
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...
Claude
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."
On 14/03/2023 11:06, Michael Osipov wrote:
Am 2023-03-14 um 01:15 schrieb Claude Brisson:
There is some work on the open issues... I'll try to get some done.
Merci, Claude !
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org
For additional commands, e-mail: dev-h...@velocity.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org
For additional commands, e-mail: dev-h...@velocity.apache.org
