Question

我已将以下内容添加到pom文件中：

<!-- Source: http://errorprone.info/docs/installation -->
<build>
    <plugins>
        <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-compiler-plugin</artifactId>
            <version>3.3</version>
            <configuration>
                <compilerId>javac-with-errorprone</compilerId>
                <forceJavacCompilerUse>true</forceJavacCompilerUse>
                <!-- maven-compiler-plugin defaults to targeting Java 5, but our javac
                     only supports >=6 -->
                <source>8</source>
                <target>8</target>
            </configuration>
            <dependencies>
                <dependency>
                    <groupId>org.codehaus.plexus</groupId>
                    <artifactId>plexus-compiler-javac-errorprone</artifactId>
                    <version>2.5</version>
                </dependency>
                <!-- override plexus-compiler-javac-errorprone's dependency on
                     Error Prone with the latest version -->
                <dependency>
                    <groupId>com.google.errorprone</groupId>
                    <artifactId>error_prone_core</artifactId>
                    <version>2.0.4</version>
                </dependency>
            </dependencies>
        </plugin>
    </plugins>
</build>

在maven clean install期间导致：

An annotation processor threw an uncaught exception.
Consult the following stack trace for details.
java.lang.NoSuchFieldError: pid
    at lombok.javac.JavacAST.packageDeclaration(JavacAST.java:107)
    at lombok.javac.JavacAST.<init>(JavacAST.java:81)
    at lombok.javac.JavacTransformer.transform(JavacTransformer.java:67)
    at lombok.javac.apt.Processor.process(Processor.java:250)
    at lombok.core.AnnotationProcessor$JavacDescriptor.process(AnnotationProcessor.java:115)
    at lombok.core.AnnotationProcessor.process(AnnotationProcessor.java:165)
    at com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:801)
    at com.sun.tools.javac.processing.JavacProcessingEnvironment.discoverAndRunProcs(JavacProcessingEnvironment.java:713)
    at com.sun.tools.javac.processing.JavacProcessingEnvironment.access$2000(JavacProcessingEnvironment.java:91)
    at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.run(JavacProcessingEnvironment.java:1021)
    at com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1129)
    at com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1141)
    at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:833)
    at com.sun.tools.javac.main.Main.compile(Main.java:249)
    at com.google.errorprone.ErrorProneCompiler.run(ErrorProneCompiler.java:220)
    at com.google.errorprone.ErrorProneCompiler.run(ErrorProneCompiler.java:158)
    at com.google.errorprone.ErrorProneCompiler.compile(ErrorProneCompiler.java:87)
    at org.codehaus.plexus.compiler.javac.errorprone.JavacCompilerWithErrorProne$CompilerInvoker.compile(JavacCompilerWithErrorProne.java:219)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:497)
    at org.codehaus.plexus.compiler.javac.errorprone.JavacCompilerWithErrorProne.performCompile(JavacCompilerWithErrorProne.java:91)
    at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:825)
    at org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:129)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
    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:116)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:347)
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154)
    at org.apache.maven.cli.MavenCli.execute(MavenCli.java:582)
    at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
    at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:497)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
[DEBUG] incrementalBuildHelper#afterRebuildExecution
[INFO] ------------------------------------------------------------------------

...

[错误]无法执行目标 org.apache.maven.plugins：Maven的编译器插件：3.3：编译项目核心（默认编译）核心：编译失败 - ＆gt; [帮助1] org.apache.maven.lifecycle.LifecycleExecutionException：失败执行目标 org.apache.maven.plugins：Maven的编译器插件：3.3：编译项目核心（默认编译）：编译失败 org.apache.maven.lifecycle.internal.MojoExecutor.execute（MojoExecutor.java:212）在 org.apache.maven.lifecycle.internal.MojoExecutor.execute（MojoExecutor.java:153）在 org.apache.maven.lifecycle.internal.MojoExecutor.execute（MojoExecutor.java:145）在 org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject（LifecycleModuleBuilder.java:116）在 org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject（LifecycleModuleBuilder.java:80）在 org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build（SingleThreadedBuilder.java:51）在 org.apache.maven.lifecycle.internal.LifecycleStarter.execute（LifecycleStarter.java:120）在org.apache.maven.DefaultMaven.doExecute（DefaultMaven.java:347）at org.apache.maven.DefaultMaven.execute（DefaultMaven.java:154）at org.apache.maven.cli.MavenCli.execute（MavenCli.java:582）at at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214）at at org.apache.maven.cli.MavenCli.main(MavenCli.java:158）at at sun.reflect.NativeMethodAccessorImpl.invoke0（Native Method）at sun.reflect.NativeMethodAccessorImpl.invoke（NativeMethodAccessorImpl.java:62）在 sun.reflect.DelegatingMethodAccessorImpl.invoke（DelegatingMethodAccessorImpl.java:43）在java.lang.reflect.Method.invoke（Method.java:497）at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced（Launcher.java:289）在 org.codehaus.plexus.classworlds.launcher.Launcher.launch（Launcher.java:229）在 org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode（Launcher.java:415）在 org.codehaus.plexus.classworlds.launcher.Launcher.main（Launcher.java:356）引起： org.apache.maven.plugin.compiler.CompilationFailureException：编译失败 org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute（AbstractCompilerMojo.java:915）在 org.apache.maven.plugin.compiler.CompilerMojo.execute（CompilerMojo.java:129）在 org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo（DefaultBuildPluginManager.java:132）在 org.apache.maven.lifecycle.internal.MojoExecutor.execute（MojoExecutor.java:208） ......还有19个[错误]

嗯..我刚刚注意到它与lombok相关的AST东西有关。

errorprone和lombok不能很好地协同工作吗？

如何解决此问题？

Answer 1

由于编译器，它们确实不能很好地协同工作。

Error-prone dev comments (Jun, 26, 2015)：

我们决定将Error Prone固定到特定版本的javac，因为Error Prone依赖于编译器内部，并且支持多个版本的javac很难并且很难验证，因为我们在内部只使用了一个版本的javac。

Lombok dev comment (Oct, 12, 2015)：

我担心Java 9支持不会在几天内得到解决。

看起来所有以2.0开头的errorprone版本都使用javac9，因此无法解决问题，尽管您可以尝试以前版本的errorprone。

Answer 2

我遇到了同样的问题，通过使用Java 8进行编译解决了这个问题（事实证明我的JAVA_HOME指向了Java 9版本。）

谷歌errorprone java编译器 - maven构建期间的bug：java.lang.NoSuchFieldError：pid

2 个答案: