[jira] [Comment Edited] (SUREFIRE-2063) Adding configuration using with --add-opens or --add-exports fails
[
https://issues.apache.org/jira/browse/SUREFIRE-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17523819#comment-17523819
]
Tibor Digana edited comment on SUREFIRE-2063 at 4/18/22 6:38 PM:
-
[~dsubel]
We have also our internal needs. Difficult to explain briefly. Unfortunatelly
non-Maven guys cannot see the release backlog, it's the Jira issue, therefore
we have published the roadmap on the Surefire site.
was (Author: tibor17):
[~dsubel]
We have also our internal needs. Difficult to explain in short. Unfortunatelly
non-Maven guys cannot see the release backlog, it's the Jira issue, therefore
we have published the roadmap on the Surefire site.
> Adding configuration using with --add-opens or --add-exports fails
>
>
> Key: SUREFIRE-2063
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2063
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 3.0.0-M6
>Reporter: Daniel Subelman
>Priority: Blocker
>
> Since v3.3.0-M6 fails when using to export or open a package. The
> failure is produced when using --add-opens or --add-exports in .
> The execution doesn't fail with v3.3.0-M5 or earlier.
> As an example, it fails when using the following :
> {code:java}
>
> --add-opens
> org.junit.platform.commons/org.junit.platform.commons.util=ALL-UNNAMED
> --add-opens
> org.junit.platform.commons/org.junit.platform.commons.logging=ALL-UNNAMED
>
> {code}
> The failure log:
> {code:java}
> [INFO] --- maven-surefire-plugin:3.0.0-M6:test (dev) @ testing ---
> [INFO] Using auto detected provider
> org.apache.maven.surefire.junitplatform.JUnitPlatformProvider
> [INFO]
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> WARNING: Unknown module: org.junit.platform.commons specified to --add-opens
> Error: Could not find or load main class --add-opens
> Caused by: java.lang.ClassNotFoundException: --add-opens
> [INFO]
> [INFO] Results:
> [INFO]
> [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 9.157 s
> [INFO] Finished at: 2022-04-06T16:28:23-04:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M6:test (dev) on project
> testing:
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Comment Edited] (SUREFIRE-2063) Adding configuration using with --add-opens or --add-exports fails
[
https://issues.apache.org/jira/browse/SUREFIRE-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17523819#comment-17523819
]
Tibor Digana edited comment on SUREFIRE-2063 at 4/18/22 6:36 PM:
-
[~dsubel]
We have also our internal needs. Difficult to explain in short. Unfortunatelly
non-Maven guys cannot see the release backlog, it's the Jira issue, therefore
we have published the roadmap on the Surefire site.
was (Author: tibor17):
[~dsubel]
We have also our internal needs. It is very difficult to explain.
Unfortunatelly non-Maven guys cannot see the release backlog, it's the Jira
issue, therefore we have published the roadmap on the Surefire site.
> Adding configuration using with --add-opens or --add-exports fails
>
>
> Key: SUREFIRE-2063
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2063
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 3.0.0-M6
>Reporter: Daniel Subelman
>Priority: Blocker
>
> Since v3.3.0-M6 fails when using to export or open a package. The
> failure is produced when using --add-opens or --add-exports in .
> The execution doesn't fail with v3.3.0-M5 or earlier.
> As an example, it fails when using the following :
> {code:java}
>
> --add-opens
> org.junit.platform.commons/org.junit.platform.commons.util=ALL-UNNAMED
> --add-opens
> org.junit.platform.commons/org.junit.platform.commons.logging=ALL-UNNAMED
>
> {code}
> The failure log:
> {code:java}
> [INFO] --- maven-surefire-plugin:3.0.0-M6:test (dev) @ testing ---
> [INFO] Using auto detected provider
> org.apache.maven.surefire.junitplatform.JUnitPlatformProvider
> [INFO]
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> WARNING: Unknown module: org.junit.platform.commons specified to --add-opens
> Error: Could not find or load main class --add-opens
> Caused by: java.lang.ClassNotFoundException: --add-opens
> [INFO]
> [INFO] Results:
> [INFO]
> [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 9.157 s
> [INFO] Finished at: 2022-04-06T16:28:23-04:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M6:test (dev) on project
> testing:
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Comment Edited] (SUREFIRE-2063) Adding configuration using with --add-opens or --add-exports fails
[
https://issues.apache.org/jira/browse/SUREFIRE-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17523443#comment-17523443
]
Daniel Subelman edited comment on SUREFIRE-2063 at 4/17/22 9:09 PM:
It's a nice find, and thanks for the PR fix.
Why the output of 3.0.0-M6 uses single quotations, but 3.0.0-M5 doesn't?
For example:
{noformat}
'--add-opens'{noformat}
vs
{noformat}
--add-opens{noformat}
was (Author: dsubel):
Nice find. Why the output of 3.0.0-M6 uses single quotations, but 3.0.0-M5
doesn't?
For example:
{noformat}'--add-opens'{noformat}
vs
{noformat}--add-opens{noformat}
> Adding configuration using with --add-opens or --add-exports fails
>
>
> Key: SUREFIRE-2063
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2063
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 3.0.0-M6
>Reporter: Daniel Subelman
>Priority: Blocker
>
> Since v3.3.0-M6 fails when using to export or open a package. The
> failure is produced when using --add-opens or --add-exports in .
> The execution doesn't fail with v3.3.0-M5 or earlier.
> As an example, it fails when using the following :
> {code:java}
>
> --add-opens
> org.junit.platform.commons/org.junit.platform.commons.util=ALL-UNNAMED
> --add-opens
> org.junit.platform.commons/org.junit.platform.commons.logging=ALL-UNNAMED
>
> {code}
> The failure log:
> {code:java}
> [INFO] --- maven-surefire-plugin:3.0.0-M6:test (dev) @ testing ---
> [INFO] Using auto detected provider
> org.apache.maven.surefire.junitplatform.JUnitPlatformProvider
> [INFO]
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> WARNING: Unknown module: org.junit.platform.commons specified to --add-opens
> Error: Could not find or load main class --add-opens
> Caused by: java.lang.ClassNotFoundException: --add-opens
> [INFO]
> [INFO] Results:
> [INFO]
> [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 9.157 s
> [INFO] Finished at: 2022-04-06T16:28:23-04:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M6:test (dev) on project
> testing:
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Comment Edited] (SUREFIRE-2063) Adding configuration using with --add-opens or --add-exports fails
[
https://issues.apache.org/jira/browse/SUREFIRE-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17523432#comment-17523432
]
Maarten Mulders edited comment on SUREFIRE-2063 at 4/17/22 7:15 PM:
I've run the project with {{mvn -X}}, and observed an interesting difference in
the output.
With Surefire 3.0.0-M5:
{code}[DEBUG] Forking command line: /bin/sh -c cd
/Users/maarten/Junk/surefire-bug/module1 &&
/Library/Java/JavaVirtualMachines/temurin-17.jdk/Contents/Home/bin/java
--add-opens
org.junit.platform.commons/org.junit.platform.commons.util=ALL-UNNAMED
--add-opens
org.junit.platform.commons/org.junit.platform.commons.logging=ALL-UNNAMED
@/Users/maarten/Junk/surefire-bug/module1/target/surefire/surefireargs3750425927935805323
/Users/maarten/Junk/surefire-bug/module1/target/surefire
2022-04-12T12-19-27_455-jvmRun1 surefire10840194083466728669tmp
surefire_017868848018900059027tmp
{code}
With Surefire 3.0.0-M6:
{code}[DEBUG] Forking command line: /bin/sh -c cd
'/Users/maarten/Junk/surefire-bug/module1' &&
'/Library/Java/JavaVirtualMachines/temurin-17.jdk/Contents/Home/bin/java'
'--add-opens'
'org.junit.platform.commons/org.junit.platform.commons.util=ALL-UNNAMED' '
--add-opens'
'org.junit.platform.commons/org.junit.platform.commons.logging=ALL-UNNAMED'
'@/Users/maarten/Junk/surefire-bug/module1/target/surefire/surefireargs18068527077933644869'
'/Users/maarten/Junk/surefire-bug/module1/target/surefire'
'2022-04-12T12-15-39_065-jvmRun1' 'surefire5839325282694079238tmp'
'surefire_01690065092548918203tmp'
{code}
Note how, with M6, the spaces (or tabs) from the POM seem to get back into the
forked JVM argument list. I've manually tried to remove them and that made the
invocation succeed. I'll create a pull request to fix this.
was (Author: mthmulders):
I've run the project with {{mvn -X}}, and observed an interesting difference in
the output.
With Surefire 3.0.0-M5:
{code}[DEBUG] Forking command line: /bin/sh -c cd
/Users/maarten/Junk/surefire-bug/module1 &&
/Library/Java/JavaVirtualMachines/temurin-17.jdk/Contents/Home/bin/java
--add-opens
org.junit.platform.commons/org.junit.platform.commons.util=ALL-UNNAMED
--add-opens
org.junit.platform.commons/org.junit.platform.commons.logging=ALL-UNNAMED
@/Users/maarten/Junk/surefire-bug/module1/target/surefire/surefireargs3750425927935805323
/Users/maarten/Junk/surefire-bug/module1/target/surefire
2022-04-12T12-19-27_455-jvmRun1 surefire10840194083466728669tmp
surefire_017868848018900059027tmp
{code}
With Surefire 3.0.0-M6:
{code}[DEBUG] Forking command line: /bin/sh -c cd
'/Users/maarten/Junk/surefire-bug/module1' &&
'/Library/Java/JavaVirtualMachines/temurin-17.jdk/Contents/Home/bin/java'
'--add-opens'
'org.junit.platform.commons/org.junit.platform.commons.util=ALL-UNNAMED' '
--add-opens'
'org.junit.platform.commons/org.junit.platform.commons.logging=ALL-UNNAMED'
'@/Users/maarten/Junk/surefire-bug/module1/target/surefire/surefireargs18068527077933644869'
'/Users/maarten/Junk/surefire-bug/module1/target/surefire'
'2022-04-12T12-15-39_065-jvmRun1' 'surefire5839325282694079238tmp'
'surefire_01690065092548918203tmp'
{code}
Note how, with M6, the spaces (or tabs) from the POM seem to get back into the
forked JVM argument list. I'll create a pull request to fix this.
> Adding configuration using with --add-opens or --add-exports fails
>
>
> Key: SUREFIRE-2063
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2063
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 3.0.0-M6
>Reporter: Daniel Subelman
>Priority: Blocker
>
> Since v3.3.0-M6 fails when using to export or open a package. The
> failure is produced when using --add-opens or --add-exports in .
> The execution doesn't fail with v3.3.0-M5 or earlier.
> As an example, it fails when using the following :
> {code:java}
>
> --add-opens
> org.junit.platform.commons/org.junit.platform.commons.util=ALL-UNNAMED
> --add-opens
> org.junit.platform.commons/org.junit.platform.commons.logging=ALL-UNNAMED
>
> {code}
> The failure log:
> {code:java}
> [INFO] --- maven-surefire-plugin:3.0.0-M6:test (dev) @ testing ---
> [INFO] Using auto detected provider
> org.apache.maven.surefire.junitplatform.JUnitPlatformProvider
> [INFO]
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> WARNING: Unknown module: org.junit.platform.commons specified to --add-opens
> Error: Could not find or load main class --add-opens
> Caused by: java.lang.ClassNotFoundException: --add-opens
> [INFO]
> [INFO] Results:
> [INFO]
>
[jira] [Comment Edited] (SUREFIRE-2063) Adding configuration using with --add-opens or --add-exports fails
[
https://issues.apache.org/jira/browse/SUREFIRE-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17521238#comment-17521238
]
Daniel Subelman edited comment on SUREFIRE-2063 at 4/12/22 4:44 PM:
[~mthmulders], thanks for reviewing the sample project that reproduces the
issue.
I look at commit
[2da8f9b3|https://github.com/apache/maven-surefire/commit/2da8f9b34da908b146e671d4b996a41bf81a9014],
and I agree that it seems to have nothing to do with the module system.
It may be related to modifying the {{maven-shared-utils}} version from [3.1.0
to
3.3.4|https://github.com/apache/maven-surefire/commit/2da8f9b34da908b146e671d4b996a41bf81a9014#diff-9c5fb3d1b7e3b0f54bc5c4182965c4fe1f9023d449017cece3005d3f90e8e4d8R99]
and/or {{org.fusesource.jansi}} dependency version from [1.13 to
2.2.0|https://github.com/apache/maven-surefire/commit/2da8f9b34da908b146e671d4b996a41bf81a9014#diff-9c5fb3d1b7e3b0f54bc5c4182965c4fe1f9023d449017cece3005d3f90e8e4d8R263].
was (Author: dsubel):
[~mthmulders], thanks for reviewing the sample project that reproduces the
issue.
I look at commit
[2da8f9b3|https://github.com/apache/maven-surefire/commit/2da8f9b34da908b146e671d4b996a41bf81a9014],
and I agree that it seems to have nothing to do with the module system.
It may be related to modifying the {{maven-shared-utils}} version from [3.1.0
to
3.3.4|https://github.com/apache/maven-surefire/commit/2da8f9b34da908b146e671d4b996a41bf81a9014#diff-9c5fb3d1b7e3b0f54bc5c4182965c4fe1f9023d449017cece3005d3f90e8e4d8R99]
and/or \{{org.fusesource.jansi }}dependency version from [1.13 to
2.2.0|https://github.com/apache/maven-surefire/commit/2da8f9b34da908b146e671d4b996a41bf81a9014#diff-9c5fb3d1b7e3b0f54bc5c4182965c4fe1f9023d449017cece3005d3f90e8e4d8R263].
> Adding configuration using with --add-opens or --add-exports fails
>
>
> Key: SUREFIRE-2063
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2063
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 3.0.0-M6
>Reporter: Daniel Subelman
>Priority: Blocker
>
> Since v3.3.0-M6 fails when using to export or open a package. The
> failure is produced when using --add-opens or --add-exports in .
> The execution doesn't fail with v3.3.0-M5 or earlier.
> As an example, it fails when using the following :
> {code:java}
>
> --add-opens
> org.junit.platform.commons/org.junit.platform.commons.util=ALL-UNNAMED
> --add-opens
> org.junit.platform.commons/org.junit.platform.commons.logging=ALL-UNNAMED
>
> {code}
> The failure log:
> {code:java}
> [INFO] --- maven-surefire-plugin:3.0.0-M6:test (dev) @ testing ---
> [INFO] Using auto detected provider
> org.apache.maven.surefire.junitplatform.JUnitPlatformProvider
> [INFO]
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> WARNING: Unknown module: org.junit.platform.commons specified to --add-opens
> Error: Could not find or load main class --add-opens
> Caused by: java.lang.ClassNotFoundException: --add-opens
> [INFO]
> [INFO] Results:
> [INFO]
> [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 9.157 s
> [INFO] Finished at: 2022-04-06T16:28:23-04:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M6:test (dev) on project
> testing:
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Comment Edited] (SUREFIRE-2063) Adding configuration using with --add-opens or --add-exports fails
[
https://issues.apache.org/jira/browse/SUREFIRE-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17521238#comment-17521238
]
Daniel Subelman edited comment on SUREFIRE-2063 at 4/12/22 4:43 PM:
[~mthmulders], thanks for reviewing the sample project that reproduces the
issue.
I look at commit
[2da8f9b3|https://github.com/apache/maven-surefire/commit/2da8f9b34da908b146e671d4b996a41bf81a9014],
and I agree that it seems to have nothing to do with the module system.
It may be related to modifying the {{maven-shared-utils}} version from [3.1.0
to
3.3.4|https://github.com/apache/maven-surefire/commit/2da8f9b34da908b146e671d4b996a41bf81a9014#diff-9c5fb3d1b7e3b0f54bc5c4182965c4fe1f9023d449017cece3005d3f90e8e4d8R99]
and/or \{{org.fusesource.jansi }}dependency version from [1.13 to
2.2.0|https://github.com/apache/maven-surefire/commit/2da8f9b34da908b146e671d4b996a41bf81a9014#diff-9c5fb3d1b7e3b0f54bc5c4182965c4fe1f9023d449017cece3005d3f90e8e4d8R263].
was (Author: dsubel):
[~mthmulders], thanks for reviewing the sample project that reproduces the
issue.
I look at commit
[2da8f9b3|https://github.com/apache/maven-surefire/commit/2da8f9b34da908b146e671d4b996a41bf81a9014],
and I agree that it seems to have nothing to do with the module system.
It may be related to modifying the {{maven-shared-utils}} version from [3.1.0
to
3.3.4|https://github.com/apache/maven-surefire/commit/2da8f9b34da908b146e671d4b996a41bf81a9014#diff-9c5fb3d1b7e3b0f54bc5c4182965c4fe1f9023d449017cece3005d3f90e8e4d8R99]
and/or \{{org.fusesource.jansi }}dependency version from 1.13 to 2.2.0.
> Adding configuration using with --add-opens or --add-exports fails
>
>
> Key: SUREFIRE-2063
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2063
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 3.0.0-M6
>Reporter: Daniel Subelman
>Priority: Blocker
>
> Since v3.3.0-M6 fails when using to export or open a package. The
> failure is produced when using --add-opens or --add-exports in .
> The execution doesn't fail with v3.3.0-M5 or earlier.
> As an example, it fails when using the following :
> {code:java}
>
> --add-opens
> org.junit.platform.commons/org.junit.platform.commons.util=ALL-UNNAMED
> --add-opens
> org.junit.platform.commons/org.junit.platform.commons.logging=ALL-UNNAMED
>
> {code}
> The failure log:
> {code:java}
> [INFO] --- maven-surefire-plugin:3.0.0-M6:test (dev) @ testing ---
> [INFO] Using auto detected provider
> org.apache.maven.surefire.junitplatform.JUnitPlatformProvider
> [INFO]
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> WARNING: Unknown module: org.junit.platform.commons specified to --add-opens
> Error: Could not find or load main class --add-opens
> Caused by: java.lang.ClassNotFoundException: --add-opens
> [INFO]
> [INFO] Results:
> [INFO]
> [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 9.157 s
> [INFO] Finished at: 2022-04-06T16:28:23-04:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M6:test (dev) on project
> testing:
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Comment Edited] (SUREFIRE-2063) Adding configuration using with --add-opens or --add-exports fails
[
https://issues.apache.org/jira/browse/SUREFIRE-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17521238#comment-17521238
]
Daniel Subelman edited comment on SUREFIRE-2063 at 4/12/22 4:42 PM:
[~mthmulders], thanks for reviewing the sample project that reproduces the
issue.
I look at commit
[2da8f9b3|https://github.com/apache/maven-surefire/commit/2da8f9b34da908b146e671d4b996a41bf81a9014],
and I agree that it seems to have nothing to do with the module system.
It may be related to modifying the {{maven-shared-utils}} version from [3.1.0
to
3.3.4|https://github.com/apache/maven-surefire/commit/2da8f9b34da908b146e671d4b996a41bf81a9014#diff-9c5fb3d1b7e3b0f54bc5c4182965c4fe1f9023d449017cece3005d3f90e8e4d8R99]
and/or \{{org.fusesource.jansi }}dependency version from 1.13 to 2.2.0.
was (Author: dsubel):
[~mthmulders], thanks for reviewing the sample project that reproduces the
issue.
I look at commit
[2da8f9b3|https://github.com/apache/maven-surefire/commit/2da8f9b34da908b146e671d4b996a41bf81a9014],
and I agree that it seems to have nothing to do with the module system.
It may be related to modifying the {{maven-shared-utils}} version from 3.1.0 to
3.3.4 and/or {{org.fusesource.jansi }}dependency version from 1.13 to 2.2.0.
> Adding configuration using with --add-opens or --add-exports fails
>
>
> Key: SUREFIRE-2063
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2063
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 3.0.0-M6
>Reporter: Daniel Subelman
>Priority: Blocker
>
> Since v3.3.0-M6 fails when using to export or open a package. The
> failure is produced when using --add-opens or --add-exports in .
> The execution doesn't fail with v3.3.0-M5 or earlier.
> As an example, it fails when using the following :
> {code:java}
>
> --add-opens
> org.junit.platform.commons/org.junit.platform.commons.util=ALL-UNNAMED
> --add-opens
> org.junit.platform.commons/org.junit.platform.commons.logging=ALL-UNNAMED
>
> {code}
> The failure log:
> {code:java}
> [INFO] --- maven-surefire-plugin:3.0.0-M6:test (dev) @ testing ---
> [INFO] Using auto detected provider
> org.apache.maven.surefire.junitplatform.JUnitPlatformProvider
> [INFO]
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> WARNING: Unknown module: org.junit.platform.commons specified to --add-opens
> Error: Could not find or load main class --add-opens
> Caused by: java.lang.ClassNotFoundException: --add-opens
> [INFO]
> [INFO] Results:
> [INFO]
> [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 9.157 s
> [INFO] Finished at: 2022-04-06T16:28:23-04:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M6:test (dev) on project
> testing:
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Comment Edited] (SUREFIRE-2063) Adding configuration using with --add-opens or --add-exports fails
[
https://issues.apache.org/jira/browse/SUREFIRE-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17520957#comment-17520957
]
Maarten Mulders edited comment on SUREFIRE-2063 at 4/12/22 7:44 AM:
Thank you, [~dsubel]!
If I did my {{git bisect}} magic correctly, this got introduced in
[{{2da8f9b3}}|https://github.com/apache/maven-surefire/commit/2da8f9b34da908b146e671d4b996a41bf81a9014].
That's a bit odd, as the commit seems to have _nothing_ to do with the module
system.
I'll see if I can do some more debugging.
was (Author: mthmulders):
Thank you, [~dsubel]!
If I did my {{git bisect}} magic correctly, this got introduced in
[{{2da8f9b3}}|https://github.com/apache/maven-surefire/commit/2da8f9b34da908b146e671d4b996a41bf81a9014].
That's a bit odd, as the commit seems to have _nothing_ to do with the module
system.
> Adding configuration using with --add-opens or --add-exports fails
>
>
> Key: SUREFIRE-2063
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2063
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 3.0.0-M6
>Reporter: Daniel Subelman
>Priority: Blocker
>
> Since v3.3.0-M6 fails when using to export or open a package. The
> failure is produced when using --add-opens or --add-exports in .
> The execution doesn't fail with v3.3.0-M5 or earlier.
> As an example, it fails when using the following :
> {code:java}
>
> --add-opens
> org.junit.platform.commons/org.junit.platform.commons.util=ALL-UNNAMED
> --add-opens
> org.junit.platform.commons/org.junit.platform.commons.logging=ALL-UNNAMED
>
> {code}
> The failure log:
> {code:java}
> [INFO] --- maven-surefire-plugin:3.0.0-M6:test (dev) @ testing ---
> [INFO] Using auto detected provider
> org.apache.maven.surefire.junitplatform.JUnitPlatformProvider
> [INFO]
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> WARNING: Unknown module: org.junit.platform.commons specified to --add-opens
> Error: Could not find or load main class --add-opens
> Caused by: java.lang.ClassNotFoundException: --add-opens
> [INFO]
> [INFO] Results:
> [INFO]
> [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 9.157 s
> [INFO] Finished at: 2022-04-06T16:28:23-04:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M6:test (dev) on project
> testing:
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Comment Edited] (SUREFIRE-2063) Adding configuration using with --add-opens or --add-exports fails
[
https://issues.apache.org/jira/browse/SUREFIRE-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17519764#comment-17519764
]
Daniel Subelman edited comment on SUREFIRE-2063 at 4/8/22 10:32 PM:
[~mthmulders], I uploaded to GitHub a minimal [sample
project|https://github.com/dsubelman/surefire-bug] that reproduces the bug.
was (Author: dsubel):
[~mthmulders], I uploaded a minimal sample
[project|https://github.com/dsubelman/surefire-bug] that reproduces the bug:
> Adding configuration using with --add-opens or --add-exports fails
>
>
> Key: SUREFIRE-2063
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2063
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 3.0.0-M6
>Reporter: Daniel Subelman
>Priority: Blocker
>
> Since v3.3.0-M6 fails when using to export or open a package. The
> failure is produced when using --add-opens or --add-exports in .
> The execution doesn't fail with v3.3.0-M5 or earlier.
> As an example, it fails when using the following :
> {code:java}
>
> --add-opens
> org.junit.platform.commons/org.junit.platform.commons.util=ALL-UNNAMED
> --add-opens
> org.junit.platform.commons/org.junit.platform.commons.logging=ALL-UNNAMED
>
> {code}
> The failure log:
> {code:java}
> [INFO] --- maven-surefire-plugin:3.0.0-M6:test (dev) @ testing ---
> [INFO] Using auto detected provider
> org.apache.maven.surefire.junitplatform.JUnitPlatformProvider
> [INFO]
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> WARNING: Unknown module: org.junit.platform.commons specified to --add-opens
> Error: Could not find or load main class --add-opens
> Caused by: java.lang.ClassNotFoundException: --add-opens
> [INFO]
> [INFO] Results:
> [INFO]
> [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 9.157 s
> [INFO] Finished at: 2022-04-06T16:28:23-04:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M6:test (dev) on project
> testing:
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Comment Edited] (SUREFIRE-2063) Adding configuration using with --add-opens or --add-exports fails
[
https://issues.apache.org/jira/browse/SUREFIRE-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17519764#comment-17519764
]
Daniel Subelman edited comment on SUREFIRE-2063 at 4/8/22 10:31 PM:
[~mthmulders], I uploaded a minimal sample
[project|https://github.com/dsubelman/surefire-bug] that reproduces the bug:
was (Author: dsubel):
[~mthmulders], I'll try to create a project that replicates the bug.
> Adding configuration using with --add-opens or --add-exports fails
>
>
> Key: SUREFIRE-2063
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2063
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 3.0.0-M6
>Reporter: Daniel Subelman
>Priority: Blocker
>
> Since v3.3.0-M6 fails when using to export or open a package. The
> failure is produced when using --add-opens or --add-exports in .
> The execution doesn't fail with v3.3.0-M5 or earlier.
> As an example, it fails when using the following :
> {code:java}
>
> --add-opens
> org.junit.platform.commons/org.junit.platform.commons.util=ALL-UNNAMED
> --add-opens
> org.junit.platform.commons/org.junit.platform.commons.logging=ALL-UNNAMED
>
> {code}
> The failure log:
> {code:java}
> [INFO] --- maven-surefire-plugin:3.0.0-M6:test (dev) @ testing ---
> [INFO] Using auto detected provider
> org.apache.maven.surefire.junitplatform.JUnitPlatformProvider
> [INFO]
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> WARNING: Unknown module: org.junit.platform.commons specified to --add-opens
> Error: Could not find or load main class --add-opens
> Caused by: java.lang.ClassNotFoundException: --add-opens
> [INFO]
> [INFO] Results:
> [INFO]
> [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 9.157 s
> [INFO] Finished at: 2022-04-06T16:28:23-04:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M6:test (dev) on project
> testing:
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
