maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tibor Digana (JIRA)" <>
Subject [jira] [Commented] (SUREFIRE-1557) Test modular build on Java 10
Date Fri, 14 Sep 2018 20:48:00 GMT


Tibor Digana commented on SUREFIRE-1557:

Hey guys, I just wanted to ping you. Do you want to include the fix in the nearest version

> Test modular build on Java 10
> -----------------------------
>                 Key: SUREFIRE-1557
>                 URL:
>             Project: Maven Surefire
>          Issue Type: Improvement
>    Affects Versions: 2.22.0
>            Reporter: Tor Egil Jacobsen
>            Assignee: Christian Stein
>            Priority: Major
> A modular build on GitHub, [jactor-rises|],
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 {{}} 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

This message was sent by Atlassian JIRA

View raw message