[
https://issues.apache.org/jira/browse/MNG-7037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17262113#comment-17262113
]
Pavel_K commented on MNG-7037:
------------------------------
[~rfscholte] Important note - I don't know maven internal work, what I can say
is the following. For my purposes I merged the following jars :
maven-artifact-3.6.3.jar
maven-builder-support-3.6.3.jar
maven-model-3.6.3.jar
maven-model-builder-3.6.3.jar
maven-repository-metadata-3.6.3.jar
into one (maven-selected) and it works just fine as JPMS module. I did it to
solve split packages problem. However, I don't know (and can't know) if there
won't be problems for other automatic modules (for example, classloader issues).
> 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)
