Robert Scholte created MCOMPILER-286:
----------------------------------------
Summary: 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
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
(v6.3.4#6332)
