org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.mysema.maven:maven-apt-plugin:1.0.2:process (default) on project sm-core: null

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Samebug tips

Do you know how to solve this issue? Write a tip to help other users and build your expert profile.

Solutions on the web

via Google Groups by kaivalya apte, 10 months ago
Failed to execute goal com.mysema.maven:maven-apt-plugin:1.0.2:process (default) on project sm-core: null
via GitHub by omarbelkhodja
, 2 years ago
Failed to execute goal com.mysema.maven:maven-apt-plugin:1.0.4:process (default) on project medicloud: java.lang.NullPointerException
via Hibernate JIRA by David J. M. Karlsen, 1 year ago
Failed to execute goal org.bsc.maven:maven-processor-plugin:2.0.5:process (default) on project pays-core-test: Error executing
via atlassian.net by Unknown author, 1 year ago
Failed to execute goal org.bsc.maven:maven-processor-plugin:2.0.5:process (default) on project pays-core-test: Error executing
via Hibernate JIRA by David J. M. Karlsen, 1 year ago
Failed to execute goal org.bsc.maven:maven-processor-plugin:2.0.5:process (default) on project pays-core-test: Error executing
via GitHub by gitgrimbo
, 2 years ago
Failed to execute goal com.github.phasebash:jsdoc3-maven-plugin:1.0.2:jsdoc3 (default) on project temp: Unable to run all JsDoc3 Tasks.
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.mysema.maven:maven-apt-plugin:1.0.2:process (default) on project sm-core: null
at com.mysema.maven.apt.AbstractProcessorMojo.execute(AbstractProcessorMojo.java:226)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)

Users with the same issue

Samebug visitor profile picture
Unknown user
Once, 2 years ago

Write tip

Know the solutions? Share your knowledge to help other developers to debug faster.