[
https://issues.apache.org/jira/browse/MCOMPILER-327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Marble updated MCOMPILER-327:
-----------------------------------
Attachment: targzdeptest.zip
> Sibling "module not found" with unrelated, non-jar dependency
> -------------------------------------------------------------
>
> Key: MCOMPILER-327
> URL: https://issues.apache.org/jira/browse/MCOMPILER-327
> Project: Maven Compiler Plugin
> Issue Type: Bug
> Affects Versions: 3.7.0
> Environment: jdk-9.0.1, maven-3.5.2, Linux
> Reporter: James Marble
> Priority: Major
> Attachments: failed_output.txt, pomdeptest.zip, targzdeptest.zip
>
>
> I have a multi-module Maven build using JDK 9. One sibling depends on
> another. Both have "module-info.java" files. This builds correctly unless the
> dependent module also has a Maven, non-jar dependency. Then
> maven-compiler-plugin fails with "module not found".
> {code:java}
> [ERROR] -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile
> (default-compile) on project problem: Compilation failure
> /home/jm6534/Documents/pomdeptest/problem/src/main/java/module-info.java:[2,24]
> module not found: pomdeptest.sibling{code}
> Attached is a minimal project that reproduces the issue and the resulting
> output.
> The build is successful if all non-jar dependencies are removed from the
> "problem" module.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
