[ 
https://issues.apache.org/jira/browse/FREEMARKER-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Benjamin Marwell updated FREEMARKER-223:
----------------------------------------
    Description: 
h2. Problem description / Motivation

All jar files should have one unique package root.
However, freemarker uses just "freemarker" as root package.
While this is not a problem, it is uncommon. It does not reflect the reverse 
domain (org.freemarker or org.apache.freemarker).

I propose this to bechanged to {{org.freemarker}} instead.

h2. Side effects.

Only for v3, the root package should be changed to "org.freemarker".
Since v3 is a major version, this is not a problem for users as breaking 
changes are expected.

With the current idea of splitting support of various technologies into new jar 
files (artifactIds) and maybe even a relocation, this could users lead to 
having multiple versions of freemarker in their class path.

However, if they know what they are doing, this could actually be an advantage 
if they need to support the old version for a bit.

h2. Related

See https://issues.apache.org/jira/browse/FREEMARKER-224 for the module name 
change.

  was:
All jar files should have one unique root.
However, freemarker uses just "freemarker" as root package.

For v3, this should be changed to "org.apache.freemarker".

That change should be reflected in FREEMARKER-222 as well, also see 
FREEMARKER-159.


> JPMS: Split package; use org.freemarker as root package
> -------------------------------------------------------
>
>                 Key: FREEMARKER-223
>                 URL: https://issues.apache.org/jira/browse/FREEMARKER-223
>             Project: Apache Freemarker
>          Issue Type: Bug
>          Components: engine
>    Affects Versions: 3.0.0
>            Reporter: Benjamin Marwell
>            Priority: Major
>
> h2. Problem description / Motivation
> All jar files should have one unique package root.
> However, freemarker uses just "freemarker" as root package.
> While this is not a problem, it is uncommon. It does not reflect the reverse 
> domain (org.freemarker or org.apache.freemarker).
> I propose this to bechanged to {{org.freemarker}} instead.
> h2. Side effects.
> Only for v3, the root package should be changed to "org.freemarker".
> Since v3 is a major version, this is not a problem for users as breaking 
> changes are expected.
> With the current idea of splitting support of various technologies into new 
> jar files (artifactIds) and maybe even a relocation, this could users lead to 
> having multiple versions of freemarker in their class path.
> However, if they know what they are doing, this could actually be an 
> advantage if they need to support the old version for a bit.
> h2. Related
> See https://issues.apache.org/jira/browse/FREEMARKER-224 for the module name 
> change.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to