ppodgorsek commented on PR #94: URL: https://github.com/apache/freemarker/pull/94#issuecomment-1783768229
@firatkucuk As you can see in the above discussion, a few points were raised: * upgrading to Jakarta means many other things must change, (that explains why the PR is so large unfortunately) * for some weird reason, `javax`/`jakarta` **must** have special treatment vs any other dependency, instead of treating it like any breaking change introduced by a major version upgrade, (with the same logic, a case could easily be made to treat any other dependency in a similar way) * the git history between versions 2 and 3 has diverged, (branch `3` did not contain all features of branch `2.3` when I worked on it, so it is likely that some fixes and new features were missed when double-merging to both release branches) * code is very difficult to read and maintain. It's unlikely FreeMarker 3 will be production-ready when/if it is released, as the unclean git history will very likely introduce regressions and bugs. Added to the fact that projects still relying on `javax` were preventing us from modernising our own, especially if `jakarta` support was very low in their priorities, we have therefore replaced FreeMarker by Thymeleaf in all projects in our organisation, bar one (but that's in progress), and have made private any public repositories based on FreeMarker, to encourage the community to switch to more modern libraries instead. It is sad to have to move away from a tool which had been so useful for decades, but a move that seems necessary unfortunately. Probably not what you wanted to read, but just my two cents. -- 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]
