You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "James Marble (JIRA)" <ji...@apache.org> on 2018/02/26 18:59:00 UTC

[jira] [Created] (MCOMPILER-327) Sibling "module not found" with unrelated, non-jar dependency

James Marble created MCOMPILER-327:
--------------------------------------

             Summary: 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
         Attachments: failed_output.txt, pomdeptest.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)