apache / apache/maven-compiler-plugin
[MCOMPILER-422] multi release jar issue exporting release version only packages
- Dominant language
- Java
- Stars
- 261
- Forks
- 191
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 8
Description
**[John Patrick](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=nhoj.patrick)** opened **[MCOMPILER-422](https://issues.apache.org/jira/browse/MCOMPILER-422?redirect=false)** and commented
I'm having to add ModuleInfoHack.java in empty packages so that compiler works, then do excludes **/ModuleInfoHack.java at package time.
The simplest example is;
```
src/main/java/package/a/Example1.java (1)
src/main/java/package/b/Example2.java (2)
src/main/java11/package/b/Example2.java (3)
src/main/java11/module-info.java (4)
```
With module-info.java looking like;
```
module MODULE_A {
exports package.a;
exports package.b;
}
```
I get compile errors so I need to create this structure adding (5);
```
src/main/java/package/a/Example1.java (1)
src/main/java/package/b/Example2.java (2)
src/main/java11/package/a/ModuleInfoHack.java (5)
src/main/java11/package/b/Example2.java (3)
src/main/java11/module-info.java (4)
```
The maven compiler plugin has this configuration;
```
java11-main
compile
compile
11
11
${project.basedir}/src/main/java11
true
```
Similar to MCOMPILER-412 it would be useful and fix my issues if target/classes is added to the compiler when doing this compiler execution.
---
**Affects:** 3.8.1
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.