[ 
https://issues.apache.org/jira/browse/SUREFIRE-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16390044#comment-16390044
 ] 

Robert Scholte commented on SUREFIRE-1497:
------------------------------------------

Looks to me like this is just in theory. If you have a module descriptor and 
you are not able to run unittests with modulepath,  then you are likely to have 
issues at runtime as well. IMHO we should only consider this if there's a 
testcase attached hitting this issue and we all agree on that such a flag is 
the only valid solution. 


> 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
>
> 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
(v7.6.3#76005)

Reply via email to