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

Posted to issues@maven.apache.org by "Hervé Boutemy (JIRA)" <ji...@apache.org> on 2018/07/28 19:44:00 UTC

[jira] [Commented] (MCOMPILER-286) Detect if dependencies should be added to classpath or modulpath

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

Hervé Boutemy commented on MCOMPILER-286:
-----------------------------------------

is this issue resolved of not?
(marked for 3.7.0...)

> Detect if dependencies should be added to classpath or modulpath
> ----------------------------------------------------------------
>
>                 Key: MCOMPILER-286
>                 URL: https://issues.apache.org/jira/browse/MCOMPILER-286
>             Project: Maven Compiler Plugin
>          Issue Type: Improvement
>    Affects Versions: 3.6.0, 3.6.1
>            Reporter: Robert Scholte
>            Assignee: Robert Scholte
>            Priority: Major
>              Labels: jigsaw
>             Fix For: 3.7.0
>
>
> With 3.6.0 if the project is a module all the dependencies end up on the modulepath. 
> It would be better to analyze every module-info.class (requires up to date ASM) and verify per dependency if it is part of the module requirements (both direct and transitive). The rest ends up on the classpath.
> Auto modules are a special chapter. Right now I would ignore auto modules to prevent collisions. Instead one could define the G:As explicitly to be added to the modulePath.



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