Tor Egil Jacobsen created SUREFIRE-1557:
-------------------------------------------
Summary: Test modular build on maven 10
Key: SUREFIRE-1557
URL: https://issues.apache.org/jira/browse/SUREFIRE-1557
Project: Maven Surefire
Issue Type: Bug
Reporter: Tor Egil Jacobsen
A modular build on GitHub,
[jactor-rises|https://github.com/jactor-rises/jactor-rises/tree/feature/junit.jupiter_configuration],
fails when running with surefire 2.22.0
All tests run perfectly fine in my IntelliJ idea. When building with maven, all
surefire reports fails with an {{InaccessableObjectException}} with message
similar to this one: {{java.lang.reflect.InaccessibleObjectException: Unable to
make com.github.jactor.rises.commons.dto.UserDtoTest() accessible: module
jactor.rises.commons does not "opens com.github.jactor.rises.commons.dto" to
unnamed module @3fc2959f}}
If one deletes all {{module-info.java}} files, the build succeeds. I thought
that during unit testing, the module should be opened by the surefire plugin.
It beats the purpose of having modular jar-files if we need to open the module
in order to test it...
Based on the issue created for the junit-team: [junit5-jupiter-starter-maven
out of date?|https://github.com/junit-team/junit5-samples/issues/81]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
