Compilation error after upgrading from 2.12.3 to 2.13.1

33 views
Skip to first unread message

Madhu Narasimhan

unread,
Feb 2, 2022, 12:41:46 PM2/2/22
to jackson-user

Hi,

I hit a strange issue after upgrading from jackson 2.12.3 to 2.13.1. With 2.13.1, compilation failed as below without any specific error message.

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project crd-lib-handlers: Compilation failure: Compilation failure: 

From the stack trace below, it appears that the compiler crashed. I know this is probably not enough information to go with, but just looking to see if anyone hit a similar problem or got any clue! (Note: If it would be of any help, I can post the Maven dependency tree for the project).

org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project crd-lib-handlers: Compilation failure

    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215)

    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)

    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)

    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)

    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)

    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)

    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)

    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)

    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)

    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)

    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)

    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)

    at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)

    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)

    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)

    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)

    at java.lang.reflect.Method.invoke (Method.java:566)

    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)

    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)

    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)

    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)

    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)

    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)

    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)

    at java.lang.reflect.Method.invoke (Method.java:566)

    at org.apache.maven.wrapper.BootstrapMainStarter.start (BootstrapMainStarter.java:39)

    at org.apache.maven.wrapper.WrapperExecutor.execute (WrapperExecutor.java:122)

    at org.apache.maven.wrapper.MavenWrapperMain.main (MavenWrapperMain.java:61)

Caused by: org.apache.maven.plugin.compiler.CompilationFailureException: Compilation failure

    at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute (AbstractCompilerMojo.java:1224)

    at org.apache.maven.plugin.compiler.CompilerMojo.execute (CompilerMojo.java:187)

    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)

    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)

    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)

    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)

    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)

    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)

    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)

    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)

    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)

    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)

    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)

    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)

    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)

    at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)

    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)

    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)

    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)

    at java.lang.reflect.Method.invoke (Method.java:566)

    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)

    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)

    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)

    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)

    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)

    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)

    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)

    at java.lang.reflect.Method.invoke (Method.java:566)

    at org.apache.maven.wrapper.BootstrapMainStarter.start (BootstrapMainStarter.java:39)

    at org.apache.maven.wrapper.WrapperExecutor.execute (WrapperExecutor.java:122)

    at org.apache.maven.wrapper.MavenWrapperMain.main (MavenWrapperMain.java:61)

[ERROR] 

[ERROR] 

[ERROR] For more information about the errors and possible solutions, please read the following articles:

[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException

Tatu Saloranta

unread,
Feb 2, 2022, 6:50:26 PM2/2/22
to jackson-user
On Wed, Feb 2, 2022 at 9:41 AM Madhu Narasimhan <madhu_na...@hotmail.com> wrote:

Hi,

I hit a strange issue after upgrading from jackson 2.12.3 to 2.13.1. With 2.13.1, compilation failed as below without any specific error message.


Errrrr.

I see:

"From the stack trace below, it appears that the compiler crashed."

and your conclusion is that Jackson upgrade somehow caused this? Even though there is nothing indicating Jackson classes?

I think you will need to do some more investigation before asking questions here about why the Jackson dependency upgrade did something that is not really supported by information presented... :)

Good luck!

-+ Tatu  +-
 
--
You received this message because you are subscribed to the Google Groups "jackson-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jackson-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jackson-user/167613be-103e-43b7-9662-755789ba787dn%40googlegroups.com.

Madhu Narasimhan

unread,
Feb 2, 2022, 8:00:06 PM2/2/22
to jackson-user
Sorry, the intention was definitely not to blame the jackson package. In fact, I saw that other groups in my company have upgraded without any problem, so knew something was out of sync in my build environment (and needed correction). As the only change I did was to update jackson version, I thought it had to do with interplay with something else I have. Wondered if some other Jackson user would have a clue based on their experience.

I did quite a bit of investigation getting nowhere, hence posted it. Agree that compiler should not ideally be put off by a new version of a package!

Thanks for the quick response.
Madhu

Tatu Saloranta

unread,
Feb 2, 2022, 10:42:05 PM2/2/22
to jackson-user
On Wed, Feb 2, 2022 at 5:00 PM Madhu Narasimhan <madhu_na...@hotmail.com> wrote:
Sorry, the intention was definitely not to blame the jackson package. In fact, I saw that other groups in my

No problem -- I did not consider it blaming but a simple request for help.
Actual breakages sometimes occur as well so it is perfectly reasonable to report such cases.
 
company have upgraded without any problem, so knew something was out of sync in my build environment (and needed correction). As the only change I did was to update jackson version, I thought it had to do with interplay with something else I have. Wondered if some other Jackson user would have a clue based on their experience.

I did quite a bit of investigation getting nowhere, hence posted it. Agree that compiler should not ideally be put off by a new version of a package!

Ok. It is sometimes difficult to know this since sometimes people post their questions with little investigation -- I am happy that yours is not such a case.

And I agree that if someone who saw the message has seen similar issues they can hopefully share their findings.

Good luck with your investigation! I know how frustrating it can be when tools do not give much information about the issue.

-+ Tatu +-

 
Reply all
Reply to author
Forward
0 new messages