maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte (JIRA)" <>
Subject [jira] [Commented] (MPLUGIN-341) Make the plugin tool modular or at least module-ready
Date Fri, 15 Jun 2018 17:48:00 GMT


Robert Scholte commented on MPLUGIN-341:

The usage of {{Automatic-Module-Name}} should only be used if the project is Java 9 ready,
but its dependencies don't have a module name yet. Both are not in place for Maven and I don't
expect it to happen. The only possibility to solve the split packages issues is to make a
monolith of it again, which is exactly the opposite of modularization. And the most interesting
Maven module is maven-compat, which will always cause split packages, and we don't want them
to return in the base code.
If Maven wants to use Java modularization, it has to be rewritten with new packages. That
would imply that *all* current plugins become useless and must be rewritten as well.
Java modules don't add much regarding reliable configuration compared to Maven. Strong encapsulation
would be cool, but that only works in combination with the module-descriptor.

> Make the plugin tool modular or at least module-ready
> -----------------------------------------------------
>                 Key: MPLUGIN-341
>                 URL:
>             Project: Maven Plugin Tools
>          Issue Type: Improvement
>    Affects Versions: 3.5.2
>            Reporter: Lukas Eder
>            Priority: Critical
> When implementing custom maven modules, it is currently not possible to make those plugins
modular on JDK 9+. The reason for this is that there are a lot of split packages among the
various libraries, such as the org.apache.maven.plugin package between:
>  * org.apache.maven:maven-core:3.5.3
>  * org.apache.maven:maven-plugin-api:3.5.3
> This, and the fact that there are not Automatic-Module-Name entries in the manifests
(see [,] means that no
one can currently reasonably create modular maven plugins.
> It would be cool if these two things could be fixed in the next minor or major release

This message was sent by Atlassian JIRA

View raw message