Google容易出错的Java编译器-Maven构建期间的错误：java.lang.NoSuchFieldError：pid

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全新安装期间，哪个导致：

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-compiler-plugin：3.3：compile（默认编译）：编译失败-> [帮助1] org.apache.maven.lifecycle.LifecycleExecutionException ：无法在项目核心上执行目标org.apache.maven.plugins：maven-compiler-plugin：3.3：compile（默认编译）：org.apache.maven.lifecycle.internal.MojoExecutor.execute（MojoExecutor。编译失败）于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.LifecycleStarter.execute（LifecycleStarter.java:120）于org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build（SingleThreadedBuilder.java:51） org.apache.maven.DefaultMaven.execute（DefaultMaven.java:154）上的.apache.maven.DefaultMaven.doExecute（DefaultMaven.java:347）在org.apache.maven.cli.MavenCli.execute（MavenCli.java:582） ）在org.apache.maven.cli.MavenCli.doMain（MavenCli.java:214）在org.apache.maven.cli.MavenCli.main（MavenCli.java:158）在sun.reflect.NativeMethodAccessorImpl.invoke0（本机方法） ）在sun.reflect.NativeMethodAccessorImpl.invoke（NativeMethodAccessorImpl.java:62）在java.lang.reflect.Method.invoke（Method.java：处）在sun.reflect.DelegatingMethodAccessorImpl.invoke（DelegatingMethodAccessorImpl.java:43）497）在org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced（Launcher.java:289）在org.codehaus.plexus.classworlds.launcher.Launcher.launch（Launcher.java:229）在org.codehaus.plexus org.codehaus.plexus.classworlds.launcher.Launcher.main（Launcher.java:356）处的.classworlds.launcher.Launcher.mainWithExitCode（Launcher.java:415）由以下原因引起：org.apache.maven.plugin.compiler.CompilationFailureException ：在org.apache的org.apache.maven.plugin.compiler.CompilerMojo.execute（CompilerMojo.java:129）的org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute（AbstractCompilerMojo.java:915）处编译失败。在org.apache.maven.lifecycle.internal.MojoExecutor.execute（MojoExecutor.java:208）上的maven.plugin.DefaultBuildPluginManager.executeMojo（DefaultBuildPluginManager.java:132）...另外19个[错误]

嗯..我刚才注意到，这是与龙目岛相关的AST东西有关的。

容易出错和龙目岛不能很好地一起工作吗？

我该怎么做才能解决这个问题？

Answer 1

我遇到了同样的问题，通过使用Java 8编译解决了它（原来我JAVA_HOME指向的是Java 9版本）。