ddekany commented on PR #96: URL: https://github.com/apache/freemarker/pull/96#issuecomment-1782425933
As of migrating away from Ant, there's already a PR for a Gradle-based solution, that keeps binary backward compatibility, while still modularizes the source code (as it's in the current 3.x). That also can handle the cases where we depend on multiple versions of the same artifact (like even of Java), which we sometimes need (in 2.x, as we have a monolithic artifact, for backward compatibility). As of the Maven package name change, I'm against thing that are annoyances for the users without bring significant new functionality in exchange. At least last time I checked, renaming a Maven group is a pain for its consumers, because then Maven won't do version conflict resolution between the old and new artifacts, and you end up having multiple version of the same classes in your application. (So you then should also rename the Java packages, but that's an even more drastic change, and should have really good reasons, like if you want to break backward compatibility in template language rules etc., as in te current 3.x.) -- 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]
