ddekany commented on PR #94: URL: https://github.com/apache/freemarker/pull/94#issuecomment-1627052476
FreeMarker always supported multiple version of Java, and multiple version of the same library (especially multiple version of the servlet API) in the same single jar. So you can add Jakarta support without removing anything, and breaking anything. Gradle doesn't change any of that (though with Gradle 2 is at least modularized on source code level). The only reason FreeMarker 2 is not modularized (unlike 3) is backward compatibility. BC is a huge pain, yes. Most users just add it as a single simple dependency, write templates, and don't care why it's working behind the scenes. But, most BC pain actually comes from issues in the template language itself, which can't be fixed without heavily breaking backward compatibility with existing templates. That's what 3 is really about (would be, if I invest the time...), although along the way it also fixes lot of historical mistakes in the API. (And 3 lives in different packages, it's not a problem if some dependency of your project uses 2, and some other uses 3.) I'm not sure what's up with Spring 6 support. Is Spring MVC FreeMarker support depend on Servlet API? Because JSP 2 "Model 2" is really old school at this point. (Besides, FreeMarker support was always a second class check box feature in Spring. First because the official choice was JSP, and then because of Thymeleaf. The only way to have proper Spring support would be to put the resources on that on the FreeMarker side.) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
