Karl Heinz Marbaise updated MCOMPILER-293:
    Fix Version/s: 3.6.2

> Add advice message in case automodules are used
> -----------------------------------------------
>                 Key: MCOMPILER-293
>                 URL: https://issues.apache.org/jira/browse/MCOMPILER-293
>             Project: Maven Compiler Plugin
>          Issue Type: Improvement
>            Reporter: Robert Scholte
>            Assignee: Robert Scholte
>             Fix For: 3.6.2
> As mentioned by the JSR-376 project lead:
> {quote}
> Strongly advise developers never to publish, for broad use, explicit modules 
> that require automatic modules.  That's risky: An automatic module is 
> unreliable, since it can depend on types on the class path, and its name and 
> exported packages could change if and when it's converted into an explicit 
> module.  It's fine to declare and use explicit modules that require automatic 
> modules in limited settings, but they should never be published to Maven 
> Central or any similar public repository.
> {quote}
> The maven-compiler-plugin should help making people aware of it. In case of 
> an application (without exported packages) the message should be at INFO 
> level, for libraries (with exported packages) the message should be at 
> warning level.

This message was sent by Atlassian JIRA

Reply via email to