[
https://issues.apache.org/jira/browse/FREEMARKER-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Marwell updated FREEMARKER-224:
----------------------------------------
Summary: JPMS: module name should be `org.apache.freemarker` (was: JPMS:
module name should be `org.freemarker`)
> JPMS: module name should be `org.apache.freemarker`
> ---------------------------------------------------
>
> Key: FREEMARKER-224
> URL: https://issues.apache.org/jira/browse/FREEMARKER-224
> Project: Apache Freemarker
> Issue Type: Bug
> Reporter: Benjamin Marwell
> Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> h2. Problem description
> Currenty, the 2.3-branch and the 3-branch are prepared (but not released yet)
> with an {{Automatic-Module-Name: freemarker}}.
> However, the consensus in the Java world is to use reverse domain names:
> https://blog.joda.org/2017/04/java-se-9-jpms-module-naming.html
> Hint: There is no need for the module name and root package to match.
> This works for both the 2.3-branch (or 2.4-branch) and the new major version.
> h2. Proposed solution
> Set the Automatic-Module-Name to either {{org.freemarker}} or maybe
> {{org.apache.freemarker}}
> h2. Side effects
> If I am not mistaken, no releases have been done with the
> {{Automatic-Module-Name}} yet. There are not side effects.
> h2. Further ideas
> If this idea works as expected, we can add a file
> {{META-INF/versions/9/module-info.class}}. This does not need to be compiled
> to Java 9, Java 7 will work just fine. But this is not in the scope of this
> issue.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
