[
https://issues.apache.org/jira/browse/SUREFIRE-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17144959#comment-17144959
]
Tibor Digana commented on SUREFIRE-1809:
----------------------------------------
[~jondruse] How you found the problem at the Line 1423? You was debugging the
plugin?
If the problem refers to the place at the Line 1423, then we should debug the
[Line
1398|https://github.com/apache/maven-surefire/blob/master/maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/AbstractSurefireMojo.java#L1398]
.
Can you show me what test in Quarkus where you have discovered this issue?
> Differences between Oracle JDK and AdoptOpenJDK caused by JPMS
> --------------------------------------------------------------
>
> Key: SUREFIRE-1809
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1809
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Failsafe Plugin, Maven Surefire Plugin
> Affects Versions: 3.0.0-M5
> Reporter: Jiri Ondrusek
> Priority: Major
>
> I was upgrading maven-surefire-plugin to 3.0.0-M5 in
> [camel-quarkus|[https://github.com/apache/camel-quarkus]] project.
> Unfortunately there was a test which was failing on CI (using AdoptOpenJDK
> build 11.0.7+10) and there was no failure on my local machine (using Oracle
> "11.0.7" 2020-04-14 LTS).
> Problem was caused by JPMS. On Orace JDK this was turned off by default. On
> AdoptOpenJDK it was turned on by default. Solution was to turn this feature
> off by configuration (https://github.com/apache/camel-quarkus/pull/1383).
> It would be nice if default behavior was the same for different Java vendors.
> Difference seems to be coming from this line -
> https://github.com/apache/maven-surefire/blob/master/maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/AbstractSurefireMojo.java#L1423
> On AdoptOpenJDK both 3 clausules are true. On Oracle JDK the last one is
> false.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
