Mapstruct implementation class not generated after upgrading to 1.36.0

[raulvaldoleiros]

After the upgrade to the version 1.36.0 the Mapstruct classes stopped from being generated, I suspect it's related with lombok upgrade.
I reverted to the previous version and it worked as expected, the shown error was:

• "No implementation was created for due to having a problem in the erroneous element java.util.ArrayList. Hint: this often means that some other annotation processor was supposed to process the erroneous element. You can also enable MapStruct verbose mode by setting -Amapstruct.verbose=true as a compilation argument."

Please let me know if I can help somehow.

[rgrunber]

We just updated to latest edge release, so maybe one of their commits is causing this ? https://github.com/projectlombok/lombok/commits/master/?since=2024-09-29&until=2024-10-31 . Maybe related to projectlombok/lombok#3116 ?

[iwangbowen]

It happened to me. At first I thought something's wrong with my code😒

[ashe98]

Facing the same issue. Any updates on this?

[mvannux]

The same for me in VSCode,
but using "mvn clean compile package" all works as expected

[laurocesar]

Rolling back to 1.35.1 version for now... Uncheck "Auto Update"

[gbrandalise]

same issue here. reverting version to 1.35.1 solve the problem.
apparently the annotationProcessorPaths does not resolving properly in correct order

[rgrunber]

Does anyone have a sample project they're able to share that easily reproduces this ? I tried just importing some basic ones from https://github.com/mapstruct/mapstruct-examples/ but I didn't see any with the error mentioned here.

When you install the latest vscode-java release (1.36.0), it will install Lombok under a path like $HOME/.vscode/extensions/redhat.java-1.36.0-linux-x64/lombok/lombok-1.18.36.jar (on Linux), or %USERPROFILE%\.vscode\extensions\redhat.java-1.36.0-win32-x64\lombok\lombok-1.18.35.jar (on Windows). That Lombok jar is the latest development version towards 1.18.35 that was available on October 31st. If you replace that jar with https://projectlombok.org/downloads/lombok.jar (currently 1.18.34), and try again, does the problem go away ? This would at least determine whether the problem is with Lombok.

[gbrandalise]

@rgrunber it's possible that the problem is related with conflicted versions of lombok?
I have vscjava.vscode-lombok extension installed and my pom.xml have following annotationProcessorPaths :

<annotationProcessorPaths>
    <path>
        <groupId>org.projectlombok</groupId>
        <artifactId>lombok</artifactId>
        <version>${lombok.version}</version>
    </path>
    <path>
        <groupId>org.projectlombok</groupId>
        <artifactId>lombok-mapstruct-binding</artifactId>
        <version>${lombok.mapstruct.binding.version}</version>
    </path>
    <!-- Mapstruct should follow the lombok path(s) -->
    <path>
        <groupId>org.mapstruct</groupId>
        <artifactId>mapstruct-processor</artifactId>
        <version>${mapstruct.version}</version>
    </path>
</annotationProcessorPaths>

[shygnome]

facing the same issue. reverting to version 1.35.1 does solve the problem.
I also have vscode-lombok extension installed.

[valtrig]

Does anyone have a sample project they're able to share that easily reproduces this ? I tried just importing some basic ones from https://github.com/mapstruct/mapstruct-examples/ but I didn't see any with the error mentioned here.

When you install the latest vscode-java release (1.36.0), it will install Lombok under a path like $HOME/.vscode/extensions/redhat.java-1.36.0-linux-x64/lombok/lombok-1.18.36.jar (on Linux), or %USERPROFILE%\.vscode\extensions\redhat.java-1.36.0-win32-x64\lombok\lombok-1.18.35.jar (on Windows). That Lombok jar is the latest development version towards 1.18.35 that was available on October 31st. If you replace that jar with https://projectlombok.org/downloads/lombok.jar (currently 1.18.34), and try again, does the problem go away ? This would at least determine whether the problem is with Lombok.

Hi, I'm also currently facing the same issue and can confirm that by simply replacing Lombok's jar in the extensions-directory with current stable version 1.18.34 does indeed make it go away.

[fbricon]

Anyone using mapstruct but not lombok can try disabling lombok support in the preferences: