[
https://issues.apache.org/jira/browse/MCOMPILER-587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17828134#comment-17828134
]
Lenny Primak commented on MCOMPILER-587:
----------------------------------------
No. I know I could reproduce it in a previous version as well.
I think it appeared with the one of the later maven 4 alpha versions though I
am not sure which exact one.
> Java Module warnings for automatic modules when used with Maven 4
> -----------------------------------------------------------------
>
> Key: MCOMPILER-587
> URL: https://issues.apache.org/jira/browse/MCOMPILER-587
> Project: Maven Compiler Plugin
> Issue Type: Bug
> Affects Versions: 3.13.0
> Environment: When used with Maven 4-alpha-13
> Reporter: Lenny Primak
> Priority: Major
>
> Looks like these warnings are generated when processing modules that have
> automatic module names in their MANIFEST.MF files.
> This only occurs with Maven 4, not maven 3. There is no way to disable these
> warnings.
> {code:java}
> [INFO] --- compiler:3.13.0:compile (default-compile) @ hope-website ---
> [WARNING] Can't extract module name from shiro-core-2.0.0-jakarta.jar: Module
> 'org.apache.shiro.core' is already on the module path!
> [WARNING] Can't extract module name from shiro-web-2.0.0-jakarta.jar: Module
> 'org.apache.shiro.web' is already on the module path!
> [WARNING] Can't extract module name from shiro-cdi-2.0.0-jakarta.jar: Module
> 'org.apache.shiro.cdi' is already on the module path! {code}
>
> Sample project: [https://github.com/lprimak/apps]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
