Hi Juan Pablo, Throughout the rather long history of the project a lot of energy has gone into maintaining backwards compatibility. I think that so long as these changes are noted in the documentation (maybe a new section?), it's probably time with the 3.0.0 transition to delineate the old and the new and consider the future more than the past. I.e., so long as users understand that we've hit that transition point I think it best to, since we have no choice to a great degree, make the changes that are necessary and not worry about sometimes decades-old legacy code and plugins, and just focus on making JSPWiki the best it can be.
My 2 cents in any case... Cheers, Murray On 1/10/25 07:28, Juan Pablo Santos Rodríguez wrote:
Hi! While going through the code I've noticed that jspwiki-api not only contained a method relying on javax, thus implying a major version), but there's also a method [#1] which uses classes from the Security Manager, marked Deprecated and for removal at a latter version (done in JDK-24, IIRC). This method is barely used throughout the code, and I suspect is less used on third party extensions. As such, I'd like to remove it from the jspwiki-api module, so we avoid a breaking change in a future release, and also remove the rest of the related deprecated code throughout the code base. This way JSPWiki should be able to run using JDK 17 to 25. Thoughts? cheers, juan pablo [#1]: https://github.com/apache/jspwiki/blob/master/jspwiki-api/src/main/java/org/apache/wiki/api/core/Session.java#L240-L252
-- ........................................................................... Murray Altheim <murray18 at altheim dot com> = = === http://www.altheim.com/murray/ === === = = === In the evening The rice leaves in the garden Rustle in the autumn wind That blows through my reed hut. -- Minamoto no Tsunenobu
