Re: Releasing Velocity Tools 3.2

2023-03-22 Thread Michael Osipov
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

Re: Releasing Velocity Tools 3.2

2023-03-22 Thread Nathan Bubna
The javax->jakarta migration is unbelievably wasteful. So much stupid. But yes, we probably have to make that a major version change. Which is also very dumb. And unfortunately, i have zero time to help. :( On Wed, Mar 22, 2023 at 3:24 AM Claude Brisson wrote: > And it should be better to

Re: Releasing Velocity Tools 3.2

2023-03-22 Thread 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). 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...