Lombok: LinkageError with Lombok, Eclipse and JasperReports Maven Plugin

[mkielar]

I'm getting a LinkageError error when opening a Maven project that utilizes jasperreports-plugin in Eclipse Mars with Lombok.

Version: Mars.1 Release (4.5.1)
Build id: 20150924-1200
Lombok v1.16.6 "Candid Duck" is installed.

In that case, whenever project is built, it runs the Maven Plugin, the Plugin seems to run correctly (no logs in Eclipse's Maven Console) and then Eclipse reports an error in pom.xml with this exception:

Error while compiling Jasper reports (com.alexnederlof:jasperreports-plugin:1.6:jasper:default:process-sources) org.apache.maven.plugin.MojoExecutionException: Error while compiling Jasper reports
    at com.alexnederlof.jasperreport.JasperReporter.executeTasks(JasperReporter.java:238)
    at com.alexnederlof.jasperreport.JasperReporter.execute(JasperReporter.java:138)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
    at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:331)
    at org.eclipse.m2e.core.internal.embedder.MavenImpl$11.call(MavenImpl.java:1362)
    at org.eclipse.m2e.core.internal.embedder.MavenImpl$11.call(MavenImpl.java:1)
    at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
    at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
    at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1360)
    at org.eclipse.m2e.core.project.configurator.MojoExecutionBuildParticipant.build(MojoExecutionBuildParticipant.java:52)
    at org.eclipse.m2e.core.internal.builder.MavenBuilderImpl.build(MavenBuilderImpl.java:137)
    at org.eclipse.m2e.core.internal.builder.MavenBuilder$1.method(MavenBuilder.java:172)
    at org.eclipse.m2e.core.internal.builder.MavenBuilder$1.method(MavenBuilder.java:1)
    at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1$1.call(MavenBuilder.java:115) 
    at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
    at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
    at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1.call(MavenBuilder.java:105)
    at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
    at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
    at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
    at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.execute(MavenBuilder.java:86)
    at org.eclipse.m2e.core.internal.builder.MavenBuilder.build(MavenBuilder.java:200)
    at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:734)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:205)
    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:245)
    at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:300)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:303)
    at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:359)
    at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:382)
    at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144)
    at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) 

Caused by: java.util.concurrent.ExecutionException: java.lang.LinkageError: loader constraint violation: when resolving method "lombok.launch.PatchFixesHider$Transform.transform_swapped(Lorg/eclipse/jdt/internal/compiler/ast/CompilationUnitDeclaration;Lorg/eclipse/jdt/internal/compiler/parser/Parser;)V" the class loader (instance of org/codehaus/plexus/classworlds/realm/ClassRealm) of the current class, org/eclipse/jdt/internal/compiler/parser/Parser, and the class loader  (instance of lombok/launch/ShadowClassLoader) for the method's defining class, lombok/launch/PatchFixesHider$Transform, have different Class objects for the type org/eclipse/jdt/internal/compiler/ast/CompilationUnitDeclaration used in the signature
    at java.util.concurrent.FutureTask.report(FutureTask.java:122)
    at java.util.concurrent.FutureTask.get(FutureTask.java:192)
    at com.alexnederlof.jasperreport.JasperReporter.checkForExceptions(JasperReporter.java:245)
    at com.alexnederlof.jasperreport.JasperReporter.executeTasks(JasperReporter.java:230) 
    ... 33 more 

Caused by: java.lang.LinkageError: loader constraint violation: when resolving method "lombok.launch.PatchFixesHider$Transform.transform_swapped(Lorg/eclipse/jdt/internal/compiler/ast/CompilationUnitDeclaration;Lorg/eclipse/jdt/internal/compiler/parser/Parser;)V" the class loader (instance of org/codehaus/plexus/classworlds/realm/ClassRealm) of the current class, org/eclipse/jdt/internal/compiler/parser/Parser, and the class loader (instance of lombok/launch/ShadowClassLoader) for the method's defining class, lombok/launch/PatchFixesHider$Transform, have different Class objects for the type org/eclipse/jdt/internal/compiler/ast/CompilationUnitDeclaration used in the signature
    at org.eclipse.jdt.internal.compiler.parser.Parser.endParse(Parser.java:8681)
    at org.eclipse.jdt.internal.compiler.parser.Parser.parse(Parser.java:9715)
    at org.eclipse.jdt.internal.compiler.parser.Parser.parse(Parser.java:9933)
    at org.eclipse.jdt.internal.compiler.parser.Parser.parse(Parser.java:9890)
    at org.eclipse.jdt.internal.compiler.parser.Parser.dietParse(Parser.java:8454)
    at org.eclipse.jdt.internal.compiler.Compiler.internalBeginToCompile(Compiler.java:718)
    at org.eclipse.jdt.internal.compiler.Compiler.beginToCompile(Compiler.java:383)
    at org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:428)
    at net.sf.jasperreports.engine.design.JRJdtCompiler.compileUnits(JRJdtCompiler.java:173)
    at net.sf.jasperreports.engine.design.JRAbstractCompiler.compileReport(JRAbstractCompiler.java:212)
    at net.sf.jasperreports.engine.JasperCompileManager.compile(JasperCompileManager.java:357)
    at net.sf.jasperreports.engine.JasperCompileManager.compileToStream(JasperCompileManager.java:326)
    at net.sf.jasperreports.engine.JasperCompileManager.compileToStream(JasperCompileManager.java:309)
    at net.sf.jasperreports.engine.JasperCompileManager.compileReportToStream(JasperCompileManager.java:587)
    at com.alexnederlof.jasperreport.CompileTask.call(CompileTask.java:75) 
    at com.alexnederlof.jasperreport.CompileTask.call(CompileTask.java:34)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at java.lang.Thread.run(Thread.java:745)

I created a small, self contained, correct example that will allow to reproduce the problem.
The problem might be that the plugin uses ejc artifact by itself, and then classes from it are loaded with a different classloader than Eclipse's, which somehow results in LinkageError.

If I remove Lombok, the whole thing complies smoothly without errors.

[nicoschl]

Hi,

Any news / workaround for this issue?

[mhagnumdw]

Today I had the same problem.

Tested versions:

• Eclipse 2019-03 with lombok in versions 1.18.12, 1.18.10, 1.18.8, 1.18.6, 1.18.4, 1.18.2, 1.18.0, 1.16.18 and edge.
• Eclipse 2020-03 with lombok 1.18.12.
• Java JDK 1.8.0_222 / Windows 10
• Maven 3.6.3
• maven plugin net.sf.jasperreports : jasperreports 6.4.3 and 6.12.2
• maven pligin com.alexnederlof : jasperreports-plugin 2.3 to 2.7

Ultimately, for this case, the solution was to remove the lombok from Eclipse. In the eclipse.ini file I removed the line -javaagent:C:\xxx\eclipse\lombok.jar

[joblini]

Any progress on this issue?

Removing Lombok from Eclipse (In the eclipse.ini file remove the line -javaagent:C:xxx\eclipselombok.jar) is not a viable solution for us as we use Lombok in many projects.

[randakar]

Looks similar to https://github.com/rzwitserloot/lombok/issues/1281 which is also still open

[randakar]

.. and https://github.com/rzwitserloot/lombok/issues/2351

Looking at this it is very important that you update not just the lombok dependency, but also the lombok installation / plugin itself, as this may be an old (closed) bug resurfacing.

Since we're now on 1.18.12 and this report is talking about a 1.16.x version this may already be fixed and just be a setup or update problem.

[randakar]

Especially with comments like this https://github.com/rzwitserloot/lombok/issues/2454#issuecomment-693176323 - you may need to refresh your workspace as well to fix this.

[joblini]

@randakar I tested with 1.18.12 in a fresh workspace, and the problem still occurs.
I created a simple project to reproduce the problem

[randakar]

Thanks.

Don't have an eclipse installation to try this on right now, but I'm sure
this will help.
Out of interest, if you're willing to test some more, can you try this
against lombok edge?
https://projectlombok.org/download-edge

On Wed, Sep 30, 2020 at 8:52 PM Ingo Jobling [e-mail]
wrote:

@randakar https://github.com/randakar I am testing with 1.18.12,
including the lombok installation / plugin itself.
I created a simple testcase to reproduce the problem : [
https://github.com/joblini/lombok-1036-test-case.git]

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/rzwitserloot/lombok/issues/1036#issuecomment-701578288,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABIERLJTAMDXGCQJYSJTR3SIN5AJANCNFSM4B4VALPQ
.

--
"Don't only practice your art, but force your way into it's secrets, for it
and knowledge can raise men to the divine."
-- Ludwig von Beethoven

[randakar]

Ok. Cloned that repo just out of curiosity and tried to compile it with
maven, but that ran into trouble because there were no properties, nor a
java compiler plugin configuration.

Does the code in this pull request:
https://github.com/joblini/lombok-1036-test-case/pull/1 solve your problem?

On Thu, Oct 1, 2020 at 1:04 PM Floris Kraak [e-mail] wrote:

Thanks.

Don't have an eclipse installation to try this on right now, but I'm sure
this will help.
Out of interest, if you're willing to test some more, can you try this
against lombok edge?
https://projectlombok.org/download-edge

On Wed, Sep 30, 2020 at 8:52 PM Ingo Jobling [e-mail]
wrote:

@randakar https://github.com/randakar I am testing with 1.18.12,
including the lombok installation / plugin itself.
I created a simple testcase to reproduce the problem : [
https://github.com/joblini/lombok-1036-test-case.git]

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/rzwitserloot/lombok/issues/1036#issuecomment-701578288,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABIERLJTAMDXGCQJYSJTR3SIN5AJANCNFSM4B4VALPQ
.

--
"Don't only practice your art, but force your way into it's secrets, for
it and knowledge can raise men to the divine."
-- Ludwig von Beethoven

--
"Don't only practice your art, but force your way into it's secrets, for it
and knowledge can raise men to the divine."
-- Ludwig von Beethoven

[joblini]

@randakar The changes in the pull request did not resolve the problem.

The error does not occur when building directly with Maven.

The error only occurs when building the project in Eclipse, via the m2e Eclipse integration
This screenshot should help to illustrate.

[joblini]

@randakar I tested with the lombok edge release (with a fresh workspace), but the problem still occurs.

[randakar]

Thanks for the testing.

Looks like someone is going to have to debug this under eclipse then.

On Thu, Oct 1, 2020, 21:18 Ingo Jobling [e-mail] wrote:

@randakar https://github.com/randakar I tested with the lombok edge
release (with a fresh workspace), but the problem still occurs.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/rzwitserloot/lombok/issues/1036#issuecomment-702344822,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABIERJCPKVHEV66VH6ZHVLSITIZHANCNFSM4B4VALPQ
.

[joblini]

When the project is built for the first time (via m2e) after running Eclipse with the lombok javaagent enabled, the error is :

java.lang.NoClassDefFoundError: org/eclipse/jdt/internal/compiler/parser/Parser
at lombok.launch.PatchFixesHider$Transform.(PatchFixesHider.java:177)

Here is the complete stack trace:

`Error while compiling Jasper reports (com.alexnederlof:jasperreports-plugin:2.6:jasper:default:process-sources)

org.apache.maven.plugin.MojoExecutionException: Error while compiling Jasper reports
at com.alexnederlof.jasperreport.JasperReporter.executeTasks(JasperReporter.java:416)
at com.alexnederlof.jasperreport.JasperReporter.execute(JasperReporter.java:210)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:332)
at org.eclipse.m2e.core.internal.embedder.MavenImpl.lambda$8(MavenImpl.java:1379)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:179)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:114)
at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1378)
at org.eclipse.m2e.core.project.configurator.MojoExecutionBuildParticipant.build(MojoExecutionBuildParticipant.java:54)
at org.eclipse.m2e.core.internal.builder.MavenBuilderImpl.build(MavenBuilderImpl.java:135)
at org.eclipse.m2e.core.internal.builder.MavenBuilder$1.method(MavenBuilder.java:169)
at org.eclipse.m2e.core.internal.builder.MavenBuilder$1.method(MavenBuilder.java:1)
at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.lambda$1(MavenBuilder.java:114)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:179)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:114)
at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.lambda$0(MavenBuilder.java:105)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:179)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:153)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:101)
at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.execute(MavenBuilder.java:88)
at org.eclipse.m2e.core.internal.builder.MavenBuilder.build(MavenBuilder.java:197)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:832)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:220)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:263)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:316)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:319)
at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:371)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:392)
at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:154)
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:244)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
Caused by: java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError: org/eclipse/jdt/internal/compiler/parser/Parser
at java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.util.concurrent.FutureTask.get(FutureTask.java:192)
at com.alexnederlof.jasperreport.JasperReporter.checkForExceptions(JasperReporter.java:423)
at com.alexnederlof.jasperreport.JasperReporter.executeTasks(JasperReporter.java:405)
... 32 more
Caused by: java.lang.NoClassDefFoundError: org/eclipse/jdt/internal/compiler/parser/Parser
at lombok.launch.PatchFixesHider$Transform.(PatchFixesHider.java:177)
at org.eclipse.jdt.internal.compiler.parser.Parser.endParse(Parser.java:9900)
at org.eclipse.jdt.internal.compiler.parser.Parser.parse(Parser.java:11077)
at org.eclipse.jdt.internal.compiler.parser.Parser.parse(Parser.java:11301)
at org.eclipse.jdt.internal.compiler.parser.Parser.parse(Parser.java:11258)
at org.eclipse.jdt.internal.compiler.parser.Parser.dietParse(Parser.java:9673)
at org.eclipse.jdt.internal.compiler.Compiler.internalBeginToCompile(Compiler.java:718)
at org.eclipse.jdt.internal.compiler.Compiler.beginToCompile(Compiler.java:383)
at org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:428)
at net.sf.jasperreports.engine.design.JRJdtCompiler.compileUnits(JRJdtCompiler.java:160)
at net.sf.jasperreports.engine.design.JRAbstractCompiler.compileReport(JRAbstractCompiler.java:203)
at net.sf.jasperreports.engine.JasperCompileManager.compile(JasperCompileManager.java:358)
at net.sf.jasperreports.engine.JasperCompileManager.compileToStream(JasperCompileManager.java:327)
at net.sf.jasperreports.engine.JasperCompileManager.compileToStream(JasperCompileManager.java:310)
at net.sf.jasperreports.engine.JasperCompileManager.compileReportToStream(JasperCompileManager.java:588)
at com.alexnederlof.jasperreport.CompileTask.call(CompileTask.java:63)
at com.alexnederlof.jasperreport.CompileTask.call(CompileTask.java:28)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.ClassNotFoundException: org.eclipse.jdt.internal.compiler.parser.Parser
at java.lang.ClassLoader.findClass(ClassLoader.java:530)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at lombok.launch.ShadowClassLoader.loadClass(ShadowClassLoader.java:534)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 21 more
`

Subsequent builds (via m2e) produce the LinkageError as indicated in the original problem description

[mhagnumdw]

Did anyone get a workaround for this problem?

[Rawi01]

Removing the eclipse lifecycle mapping should help here. The problem is that the jasperreports plugin loads the eclipse compiler classes every time you run a m2e build and lombok does not like that.

[joblini]

The purpose of the m2e lifecycle mapping is to invoke the jasperreports plugin to compile reports, as required, during the Eclipse build cycle. Removing the mapping would result in reports not being compiled, so this isn't an acceptable solution.

[Rawi01]

You can still invoke the maven goal by hand or compile the reports using your reports editor (e.g. Jaspersoft Studio). That might not be perfect but is still a better workaround than removing lombok completly.