You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tibor Digana (Jira)" <ji...@apache.org> on 2019/11/16 10:24:00 UTC
[jira] [Commented] (SUREFIRE-1497) Flag to select modulepath or
classpath
[ https://issues.apache.org/jira/browse/SUREFIRE-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16975659#comment-16975659 ]
Tibor Digana commented on SUREFIRE-1497:
----------------------------------------
[~scolebourne@joda.org]
Not sure if the users know that your requirement to switch on/off the modular classpath exists since of the version 3.0.0-M2.
See the configuraion parameter {{useModulePath}} in documentation. The default value for this parameter is {{true}}.
Pls se it to {{false}} if it has to solve your problem.
> Flag to select modulepath or classpath
> --------------------------------------
>
> Key: SUREFIRE-1497
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1497
> Project: Maven Surefire
> Issue Type: Improvement
> Affects Versions: 2.21.0
> Reporter: Stephen Colebourne
> Priority: Major
> Labels: jigsaw
> Attachments: maven-issue4.zip
>
>
> SUREFIRE-1262 added the ability to run tests using the modulepath, which is great. However, as a library developer I cannot guarantee that the code will be run on the modulepath, it might well be run on the classpath.
> As such, can I request a flag that turns the behaviour in SUREFIRE-1262 on and off? This would allow a single pom.xml to run surefire twice, once with the code on the modulepath and once with the code on the classpath, to ensure that the behaviour always works however the code is run. (Other solutions to achieve the same goal may be possible, but this seems the most obvious).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)