maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte (JIRA)" <>
Subject [jira] [Closed] (MNG-6516) Build maven-mojo using Java9 fails
Date Fri, 23 Nov 2018 08:49:00 GMT


Robert Scholte closed MNG-6516.
    Resolution: Not A Problem
      Assignee: Robert Scholte

{quote}... Maven has its own modular system long before the Java Platform Modular 
 System (JPMS).
 Due to the evolution of Maven over the last decade there are indeed split 
 packages, which was never an issue.
 Cleaning up is simply not possible and not necessary, unless we make a 
 monolith of it, which is actually the opposite of want you want to achieve 
 with modularization.
 Cleaning up would mean introducing new packages, which would effectively 
 make all current maven-plugins useless.
 For that reason I see no reason to make it JPMS-modular.

> Build maven-mojo using Java9 fails
> ----------------------------------
>                 Key: MNG-6516
>                 URL:
>             Project: Maven
>          Issue Type: Bug
>          Components: Plugin API
>         Environment: java 9
>            Reporter: Matthias Fuchs
>            Assignee: Robert Scholte
>            Priority: Major
>              Labels: java9, modules
> I'm upgrading my Java8 framework to Java9, but I have major problems upgrading my mojos
> The problem is that my dependecies maven-artifact a maven-core contain the same classes.
This causes the java9 compiler to fail. It also seems that those libraries haven't been upgraded
to use or at least automatic module name in META-INF.
> Expected solution:
> restructure the libraries to conform to the java module system.

This message was sent by Atlassian JIRA

View raw message