maven-compiler-plugin: Switch from 3.11.0 >= 3.11.0 causes my org.openapitools.openapi-generator:7.11.0 to suddenly fail

[MarcelEdmundFranke]

Affected version

3.12.0, 3.13.0, 3.14.0

Bug description

After upgrading the maven-compiler-plugin from version 3.11.0 to any version >= 3.11.0, the OpenAPI Generator (org.openapitools:openapi-generator-maven-plugin:7.11.0) fails during the build process. The error occurs consistently across all generated OpenAPI source files.

Error Message (example):

[ERROR] /Users/xxx/workspace/xxx/xxx/target/generated-sources/openapi/src/main/java/com/example/project/model/MaskedDto.java: error reading /Users/xxx/workspace/xxx/xxx/target/generated-sources/openapi/src/main/java/com/example/project/model/MaskedDto.java; /Users/xxx/workspace/xxx/xxx/target/generated-sources/openapi/src/main/java/com/example/project/model/MaskedDto.java

This issue affects all OpenAPI-generated files, not just the one shown above.

Steps to Reproduce:

1. Use openapi-generator-maven-plugin version 7.11.0 to generate sources.
2. Set maven-compiler-plugin to any version >= 3.11.0.
3. Run mvn clean install.

Observe the build failure with file read errors on generated sources.

Expected Behavior:

The build should succeed without file read errors when using maven-compiler-plugin versions >= 3.11.0.

Workaround:

Reverting to maven-compiler-plugin version 3.11.0 resolves the issue.

Environment:

Maven: 3.9.10
Java: 21
OS: macOS 15.5
OpenAPI Generator: 7.11.0 - Upgrading to 7.14.0 is not fixing this
maven-compiler-plugin: >= 3.11.0 (issue), 3.11.0 (works)

[cdouillard]

HI @MarcelEdmundFranke,

Maybe you are experiencing the same issue as described in #874.

Can you provide more information about the configuration of the maven-compiler-plugin in your project ? Are you using the generatedSourcesDirectory parameter to specify where the source files are generated by the openapi-generator-maven-plugin?

[MarcelEdmundFranke]

Hi @cdouillard, I followed the instructions and this solution fixed my issue.

[MarcelEdmundFranke]

Hi @cdouillard again,

It fixed one but opened a new issue....

I'm encountering a new compilation error only in our Azure Pipeline but in not locally. The error is:

[INFO] -------------------------------------------------------------
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] /home/vsts/work/1/s/xxx/target/generated-sources/annotations/de/xxx/bb/xxx/out/mapper/XXXMapperImpl.java: error reading ...XXXMapperImpl.java

This issue affects only this specific mapper (XXXImpl.java). All other mappers compile successfully both locally and in CI.

Config

<plugin>
                    <groupId>org.apache.maven.plugins</groupId>
                    <artifactId>maven-compiler-plugin</artifactId>
                    <version>${maven-compiler-plugin.version}</version>
                    <configuration>
                        <annotationProcessorPaths>
                            <path>
                                <groupId>org.projectlombok</groupId>
                                <artifactId>lombok</artifactId>
                                <version>${org.projectlombok.version}</version>
                            </path>
                            <path>
                                <groupId>org.projectlombok</groupId>
                                <artifactId>lombok-mapstruct-binding</artifactId>
                                <version>${org.lombok-mapstruct-binding.version}</version>
                            </path>
                            <path>
                                <groupId>org.mapstruct</groupId>
                                <artifactId>mapstruct-processor</artifactId>
                                <version>${org.mapstruct.version}</version>
                            </path>
                        </annotationProcessorPaths>
                        <release>${java.version}</release>
                    </configuration>
                </plugin>

Any ideas or suggestions would be appreciated
Thanks!

[cdouillard]

Hi @MarcelEdmundFranke ,

Can you provide more information about :

• the java version and distribution you are using locally and the one used by your Azure pipeline
• the mapstruct version

Can you add the following option to your maven-compiler-plugin configuration : <verbose>true</verbose>.

If you can, please run maven with the --debug option on your Azure pipeline : mvn clean compile --debug.

Thanks.

[MarcelEdmundFranke]

Hi @cdouillard

• Java version is 21 (Local: Temurin-21.0.5+11 and Azure: RHEL10)
• Mapstruct version is 1.6.3
• mapstruct-binding is 0.2.0

"If you can, please run maven with the --debug option on your Azure pipeline : mvn clean compile --debug."

Done. Could you point me to the log statement you're interested in?

Maybe this

Processor org.mapstruct.ap.MappingProcessor matches [/org.mapstruct.Mapper] and returns false.
[parsing started DirectoryFileObject[/home/vsts/work/1/s/adapter-outbound/target/generated-sources/annotations:de/xxx/bb/tasklist/out/mapper/TaskPCfConnectorMapperImpl.java]]
[parsing completed 2ms]
Round 2:
	input files: {de.xxx.bb.tasklist.out.mapper.TaskPCfConnectorMapperImpl}
	annotations: [javax.annotation.processing.Generated, org.springframework.stereotype.Component, java.lang.Override]
	last round: false
Processor lombok.launch.AnnotationProcessorHider$AnnotationProcessor matches [/org.springframework.stereotype.Component, java.compiler/javax.annotation.processing.Generated, java.base/java.lang.Override] and returns false.
Processor lombok.launch.AnnotationProcessorHider$ClaimingProcessor matches [] and returns true.
Processor org.mapstruct.ap.MappingProcessor matches [] and returns false.
Round 3:
	input files: {}
	annotations: []
	last round: false
Processor lombok.launch.AnnotationProcessorHider$AnnotationProcessor matches [] and returns false.
Processor lombok.launch.AnnotationProcessorHider$ClaimingProcessor matches [] and returns true.
Processor org.mapstruct.ap.MappingProcessor matches [] and returns false.
Round 4:
	input files: {}
	annotations: []
	last round: false
Processor lombok.launch.AnnotationProcessorHider$AnnotationProcessor matches [] and returns false.
Processor lombok.launch.AnnotationProcessorHider$ClaimingProcessor matches [] and returns true.
Processor org.mapstruct.ap.MappingProcessor matches [] and returns false.
Round 5:
	input files: {}
	annotations: []
	last round: false
Processor lombok.launch.AnnotationProcessorHider$AnnotationProcessor matches [] and returns false.
Processor lombok.launch.AnnotationProcessorHider$ClaimingProcessor matches [] and returns true.
Processor org.mapstruct.ap.MappingProcessor matches [] and returns false.
Round 6:
	input files: {}
	annotations: []
	last round: true

[MarcelEdmundFranke]

Hi @cdouillard again,

I added -Dmaven.compiler.useIncrementalCompilation=false in azure, and with this option enabled, the build works. Without it, it fails. Why is that?

Edit

Or deleting the target folder in the module.

[MarcelEdmundFranke]

Hi, Any updates on this?

[cdouillard]

Hi @MarcelEdmundFranke,

I try to reproduce your problem but didn't manage to do it. It's complicated to analyze the problem witouth a reproducer.

Maybe we can summarize what was done since the issue was opened to better understand the problem.

What was your maven-compiler-plugin configuration when you opened the issue ? Did you use the generatedSourcesDirectory parameter ? If you use a parent in your pom.xml, it can be interesting to see the maven-compiler-plugin configuration on the effective pom as some configuration can be inherited from the parent.

Do you declare any other plugin that references generated-sources ? How do you configure the openapi-generator-maven-plugin ?

What is your Azure pipeline doing ? Which maven command is it executing ?