[
https://issues.apache.org/jira/browse/SUREFIRE-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16601674#comment-16601674
]
Christian Stein commented on SUREFIRE-1563:
-------------------------------------------
{quote}Seems natural for {{src/test/main}} to have its own {{module-info.java}}
{quote}
You mean {{src/test/*java*}}, don't you? "test/main" seems to contradict itself.
{quote}Strangely enough, if I put a {{=}} instead of the space, just after
{{-patch-module}}, it seems to work ?!?
{quote}
Definitely strange. The {{javac}} doc cleary shows a space:
[https://docs.oracle.com/javase/10/tools/javac.htm] (For {{java}} the same.)
All in all your thoughts show that test modules are something that should be
treated a first-class citizens in the Java module system.
> 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)
