apache / apache/maven-compiler-plugin
[MCOMPILER-444] Dependency that should be on modulepath sometime put on classpath
- Dominant language
- Java
- Stars
- 261
- Forks
- 191
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 8
Description
**[Benjamin Marwell](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=mampf86)** opened **[MCOMPILER-444](https://issues.apache.org/jira/browse/MCOMPILER-444?redirect=false)** and commented
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:
> [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
demo project: https://github.com/bmarwell/jaxrs-surefire-module-showcase
---
**Affects:** 3.8.1
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.