[
https://issues.apache.org/jira/browse/MNG-7037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17261950#comment-17261950
]
Pavel_K commented on MNG-7037:
------------------------------
[~rfscholte] From here https://stackoverflow.com/a/46504438/5057736
There are two ways to infer an automatic module's name:
entry in the manifest
guess from the JAR file name
In the first case, the name was deliberately picked by the maintainer, so it
can be assumed to be stable *(for example it doesn't change when the project
gets modularized)*.
As I said, automatic modules are used as a phase 1 when project (library) can
be used in JPMS environment, however project is not modularized according to
JPMS (phase 2).
> 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)
