You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Christian Stein (JIRA)" <ji...@apache.org> on 2018/11/22 11:05:00 UTC

[jira] [Commented] (MCOMPILER-365) Missing main classes when test contains a module descriptor

    [ https://issues.apache.org/jira/browse/MCOMPILER-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16695774#comment-16695774 ] 

Christian Stein commented on MCOMPILER-365:
-------------------------------------------

Follow-up from https://issues.apache.org/jira/browse/MCOMPILER-341

> Missing main classes when test contains a module descriptor
> -----------------------------------------------------------
>
>                 Key: MCOMPILER-365
>                 URL: https://issues.apache.org/jira/browse/MCOMPILER-365
>             Project: Maven Compiler Plugin
>          Issue Type: Improvement
>    Affects Versions: 3.8.0
>            Reporter: Christian Stein
>            Assignee: Christian Stein
>            Priority: Minor
>
> When `testCompile` detects a `module-info.java` file it patches the sources from the main set into the test compilation process. This yields a) recompiling main source files and b) leaves out not directly referenced main types.
> I would be better to re-use _all_ compiled type from the main source set, if possible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)