[
https://issues.apache.org/jira/browse/SUREFIRE-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16981206#comment-16981206
]
Tibor Digana edited comment on SUREFIRE-1497 at 11/24/19 11:34 PM:
-------------------------------------------------------------------
[[email protected]]
Thank you for your reply. We can fix the issues with the user feedback
therefore pls help us with the following investigation:
Pls run your build, using e.g. {{mvn -X test}}, with the debug logs and see the
CLI comand. Pls reply back and tell me how you would like the CLI command to
have in order to make the issue SUREFIRE-1563 working properly for you. Thx
I will close this issue.
was (Author: tibor17):
[[email protected]]
Thank you for your reply. We can fix the issues with the user feedback
therefore pls help us with the following investigation:
Pls run your build, using e.g. {{mvn -X test}}, with the debug logs and see the
CLI comand. Pls reply back and tell me how you would like to have the CLI
command to make the issue SUREFIRE-1563 working properly for you. Thx
I will close this issue.
> 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)
