[
https://issues.apache.org/jira/browse/SUREFIRE-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16599607#comment-16599607
]
Christian Stein commented on SUREFIRE-1563:
-------------------------------------------
{quote}If it would be a module-info, it would put everything back on the
modulepath, I don't like that.
{quote}
But JUnit and friends (all other testing-related frameworks and tools) want to
live on the module-path, too! They only want to export some packages to test,
extension and engine authors. Why would you limit JUnit and friends to live on
the classpath when it comes to whitebox testing?
{quote}People need to learn the module system.
{quote}
True.
> NoClassDefFoundError for JPMS modules with "require static"
> -----------------------------------------------------------
>
> Key: SUREFIRE-1563
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1563
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
> Affects Versions: 2.22.0
> Reporter: Simone Bordet
> Priority: Major
> Attachments: maven-jpms.tgz
>
>
> When a Maven module has a {{module-info.java}} that contains a {{requires
> static}}, Surefire throws {{NoClassDefFoundError}} when running the tests for
> that Maven module.
> If the dependency is declared only as {{required}} (no {{static}}), then the
> tests run fine.
> Attached a reproducible project.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
