[
https://issues.apache.org/jira/browse/SUREFIRE-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16601677#comment-16601677
]
Simone Bordet commented on SUREFIRE-1563:
-----------------------------------------
{quote}
You mean src/test/java, don't you?
{quote}
Ah, yes.
{quote}
All in all your thoughts show that test modules are something that should be
treated a first-class citizens in the Java module system.
{quote}
I think the JDK has a solution in {{--patch-module}}. I doubt they'll do
something more.
The problem are the tools, from IDEs to Maven, as they have to be aware of test
{{module-info.java}} and treat it differently from a source
{{module-info.java}}.
There is the need to agree on some specification that defines the exact
semantic, and then all the tools must pick it up consistently.
> 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)
