[
https://issues.apache.org/jira/browse/MCOMPILER-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15973555#comment-15973555
]
Hudson commented on MCOMPILER-286:
----------------------------------
FAILURE: Integrated in Jenkins build maven-plugins #8932 (See
[https://builds.apache.org/job/maven-plugins/8932/])
[MCOMPILER-286] Detect if dependencies should be added to classpath or
modulepath
ASM 6.0_ALPHA2 not released, can't use its features yet. (rfscholte:
[http://svn.apache.org/viewvc/?view=rev&rev=1791835])
* (edit)
maven-compiler-plugin/src/main/java/org/apache/maven/plugin/compiler/module/AsmModuleInfoParser.java
> 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
> Labels: jigsaw
>
> 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.15#6346)
