[jira] [Commented] (MNG-7037) Add JPMS support -> solve split packages problem

["Paul Scholz (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MNG-7037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17343151#comment-17343151 ] 

Paul Scholz commented on MNG-7037:
----------------------------------

I can confirm [~Pavel_K]'s workaround works.

Just to get a clearification on some details,
 * what would be a alternative to using the internal Util mentioned by Pavel (as provided by the resolver examples; [~rfscholte] )
 * if the resovler project is independent, why is it some how depending on "core" maven artifacts?

> 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)