[
https://issues.apache.org/jira/browse/SUREFIRE-1731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16987839#comment-16987839
]
John Patrick commented on SUREFIRE-1731:
----------------------------------------
https://issues.apache.org/jira/browse/SUREFIRE-1234 is along the same lines..
regarding avatar... it's a true reflection... well it was ~10-20 years ago when
i started using it
`--add-opens` not sure if that is still needed, it solved some issues a few
releases ago of both surefire and junit, will see if it's still needed.
yep is surefire and failsafe both allowed toolchains for configuration and per
execution configuration that would be useful
> Unable to test Multi Release Jar with surefire or failsafe
> ----------------------------------------------------------
>
> Key: SUREFIRE-1731
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1731
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Failsafe Plugin, Maven Surefire Plugin
> Affects Versions: 2.22.2, 3.0.0-M4
> Reporter: John Patrick
> Priority: Major
>
> I'm creating a Multi Release jar, containing base Java 1.8 and Java 11
> classes. But am not able to successful test the Java 11 part.
> In the following repo, I've got 3 tests.
> * 1 test needs to be executed using Java 1.8 that are under src/test/java.
> * 2 tests need to be executed using Java 11 that are under src/test/java11.
> If the src/test/java tests are executed using Java 11 I expect it to fail
> which is expected, because it would be picking up the classes under
> target/classes/META-INF/versions/11/ and not the Java 1.8 version under
> target/classes/. Because the tests have been written to prove the correct
> source file is used for execution so the Java 1.8 BaseClass returns a
> different string to the Java 11 BaseClass.
> [https://github.com/nhojpatrick/issue-maven-multi-release-jar-testing]
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
