[MNG-7037] Add JPMS support -> solve split packages problem

**[Pavel_K](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=pavel_k)** opened **[MNG-7037](https://issues.apache.org/jira/browse/MNG-7037?redirect=false)** and commented

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.

---

**Affects:** 3.6.3

**Issue Links:**
- [MNG-7089](https://issues.apache.org/jira/browse/MNG-7089) Add module-info.java to the project
(_**"is duplicated by"**_)
- [MNG-7497](https://issues.apache.org/jira/browse/MNG-7497) Split Packages in Maven Model Builder
(_**"is duplicated by"**_)

2 votes, 5 watchers

Start by reading the linked MNG-7089 and MNG-7497 issues, which cover adding module-info.java and the Maven Model Builder split packages problem. Determine the agreed JPMS scope and confirm that the affected Maven modules no longer produce split packages or module-resolution failures.

Written by the indexing model from the issue text.