You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Robert Scholte (JIRA)" <ji...@apache.org> on 2018/01/27 13:55:00 UTC

[jira] [Closed] (MRESOLVER-41) JDK 9 - Module Auto Naming conflict - maven.resolver.api please repackage the code inside with org.apache.maven.resolver.api

     [ https://issues.apache.org/jira/browse/MRESOLVER-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Scholte closed MRESOLVER-41.
-----------------------------------
    Resolution: Won't Fix
      Assignee: Robert Scholte

The Automatic module name is {{org.apache.maven.resolver}}. 
And yes, we are aware that the packages are not in sync, but that's for a good reason. Eclipse allowed us to *only* use the name {{Aether}} to prevent compatibility issues. And we already have bad experiences with repackaging when going from Sonatype to Eclipse.
We are not allowed to use this name in any other case, so we won't add Aether to the module name, nor are we going to repackage.


> JDK 9 - Module Auto Naming conflict - maven.resolver.api please repackage the code inside with org.apache.maven.resolver.api
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MRESOLVER-41
>                 URL: https://issues.apache.org/jira/browse/MRESOLVER-41
>             Project: Maven Resolver
>          Issue Type: Bug
>          Components: resolver
>    Affects Versions: Maven Artifact Resolver 1.2.0 pre-reset, Maven Artifact Resolver 1.1.0, Maven Artifact Resolver 1.1.1
>         Environment: JDK 9, JDK 9.1, JDK 10
>            Reporter: Pratik Parikh
>            Assignee: Robert Scholte
>            Priority: Major
>
> Include the following in {{pom.xml}}.
> {code:xml}
> <dependency>
>  <groupId>org.apache.maven.resolver</groupId>
>  <artifactId>maven-resolver-api</artifactId>
>  <version>1.1.0</version>
> </dependency>
> {code}
> add the following requires line in your {{module-info.java}}
> {code}
> requires maven-resolver-api
> {code}
> The module won't resolve this is due the fact that internal package name is different then outer one. Ideally both should match.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)