[
https://issues.apache.org/jira/browse/MCOMPILER-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17248012#comment-17248012
]
Benjamin Marwell commented on MCOMPILER-444:
--------------------------------------------
If I instead use jakarta.xml.bind:jakarta.xml.bind-api:2.3.3:test, I get:
[ERROR] module not found: java.xml.bind.
Huh…
> Dependency that should be on modulepath sometime put on classpath
> -----------------------------------------------------------------
>
> Key: MCOMPILER-444
> URL: https://issues.apache.org/jira/browse/MCOMPILER-444
> Project: Maven Compiler Plugin
> Issue Type: Bug
> Affects Versions: 3.8.1
> Reporter: Benjamin Marwell
> Priority: Major
>
> See https://issues.apache.org/jira/browse/MCOMPILER-336
> I can still recreate this with a test dependency.
> I believe the jakarta.activation module should have been on the module path,
> but is only on the classpath. This leads to this error:
> {quote}[ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.8.1:testCompile
> (default-testCompile) on project surefire-module-test: Compilation failure
> [ERROR] module not found: jakarta.activation
> {quote}
> demo project: [https://github.com/bmarwell/jaxrs-surefire-module-showcase]
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
