[
https://issues.apache.org/jira/browse/SUREFIRE-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17784192#comment-17784192
]
David M. Lloyd commented on SUREFIRE-1618:
------------------------------------------
We've also hit this issue. [~marx.freedom], WDYT about opening a pull request
with the given patch at https://github.com/apache/maven-surefire ? It seems OK
to me.
> Configure module path with additional modules
> ---------------------------------------------
>
> Key: SUREFIRE-1618
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1618
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Surefire Plugin
> Affects Versions: 3.0.0-M3
> Reporter: Sergey Gurev
> Priority: Major
> Attachments: additionalModules.patch
>
>
> When surefire-maven-plugin runs tests with the JPMS it constructs module path
> only from modules required by compiled module (reading its descriptor from
> file target/classes/module-info.class). Other jars will be used in class path
> even they are modular (with module-info.class).
> It seems that plugin should include all modular jars to module path or there
> should be an option to configure module path.
> For example:
>
> {code:java}
> <additionalModules>
> <additionalModule>net.bytebuddy</additionalModule>
> <additionalModule>net.bytebuddy.agent</additionalModule>
> </additionalModules>
> {code}
>
> Attached patch contains implementation of "additionalModules" configuration
> property.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
