[
https://issues.apache.org/jira/browse/SUREFIRE-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16583708#comment-16583708
]
Robert Scholte commented on SUREFIRE-1497:
------------------------------------------
I've been thinking about this, shouldn't this be a failsafe option only? Just
me keep the difference clear between unittesting and integrationtesting. For
the same reason you can and should test multirelease jars with failsafe only
(MRJARs doesn't work with the classes-directory, it _*must*_ be a jar)
> 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
(v7.6.3#76005)
