[
https://issues.apache.org/jira/browse/MNG-7037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17261879#comment-17261879
]
Pavel_K commented on MNG-7037:
------------------------------
[~rfscholte] There are different module types
(https://github.com/tfesenko/Java-Modules-JPMS-CheatSheet):
# explicit named (with module-info, with exports/opens and internal packages)
# automatic named (without module-info, module exports all packages and also
opens them for deep reflection)
As maven is old, it can be difficult to create explicit modules with open and
hidden packages. However, it is absolutely possible to create automatic modules
- the only thing that is required is to solve split package problem.
So, it is not necessary to change package access - that can be really very
difficult. The first phase is just to remove split package [+ add automatic
module name]. Many library go this way - firstly they create automatic modules
and then, if they have resources and if it necessary they create explicit
modules, for example Jetty (AFAIR).
However, "we won't support JPMS" decision is a wrong one, because all libraries
and programs that plan to develop (not to die) slowly add JPMS support.
> Add JPMS support -> solve split packages problem
> ------------------------------------------------
>
> Key: MNG-7037
> URL: https://issues.apache.org/jira/browse/MNG-7037
> Project: Maven
> Issue Type: Improvement
> Affects Versions: 3.6.3
> Reporter: Pavel_K
> Priority: Minor
>
> I use apache maven with apache maven resolver in JPMS environment as
> automatic modules. At least I wanted to use them this way. When I started my
> application I got
> java.lang.module.ResolutionException: Modules maven.model.builder and
> maven.model export package org.apache.maven.model.merge to module
> mymodule.core.
> Please, add JPMS support. 2020 is ending and there are still split packages.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
