ddekany commented on PR #94: URL: https://github.com/apache/freemarker/pull/94#issuecomment-1800287771
So, we have to chose out which end result (ignore the "how" for now): 1. We can copy the `freemarker.ext.servlet` package into `freemarker.ext.jakartaservlet`, and we will have it the normal artifact. 2. We can have an additional artifact variant (let's say via Maven classifier "jakarta"), that still uses `freemarker.ext.servlet` package, but that links to the Jakarta classes. Possibility 1 has the pro that we don't have to publish one more artifact, and also, then users don't have to fiddle with dependency management to chose the "jakarta" classifier artifact. But it has the con, that any existing dependent Java code that used `freemarker.ext.servlet` so far, and wants to migrate to a Jakarta Servlet container, has to be modified to link to `freemarker.ext.jakartaservlet` instead. That sounds quite bad, however, the same dependent Java code likely has to be modified anyway, to link to Jakarta Servlet classes. `web.xml`-s that refer to `freemarker.ext.servlet.FreemarkerSerlvet` also have to be modified, if someone uses a Jakarta container. Actually, I will bring it up on the mailing list... if you are also there, please answer there. -- 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]
