[
https://issues.apache.org/jira/browse/MNG-7037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17426770#comment-17426770
]
Robert Scholte commented on MNG-7037:
-------------------------------------
Renaming will likely break things. I think I will repeatr myself, but Maven
should introduce new api and spi artifacts, with their own package. Developers
should only use these and eventually there's no need to push the
implementation to Central anymore, because that's part of the Apache Maven
distribution.
> 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)
