bmarwell commented on PR #98:
URL: https://github.com/apache/freemarker/pull/98#issuecomment-1793476492
> Actually, as of more practical problems, I suspect 2 doesn't even work
properly when used as a module, as it should static import a few stuff for it,
like logging frameworks
That's not a concern. Automatic modules will get access to everything and
export everything. You can't create a jlink distribution with automatic modules.
Therefore it doesn't break anything because no one could have used
freemarker as a module before the version where you introduced the automatic
module name.
> As of "3", I believe there we simply need {{module-info.java-s}} in all
projects.
That's definitely the best solution.
> (Not sure about OSGi support, and if we will support it at all, or it will
be practically dead by the time FM3 released, if ever.)
OSGi is actually more widely used compared to JPMS modules. It's better
defined, more Flexible and has been around for longer. I myself don't use it.
But that would be a great question on the user mailing list.
--
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]
