Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Not compatible with google's error-prone

Description

When the processor is used alongside google's error-prone processor, I get:

19:52:50 compiler message file broken: key=compiler.misc.msg.bug arguments=11, {1}, {2}, {3}, {4}, {5}, {6}, {7} 19:52:50 java.lang.NoSuchMethodError: com.google.common.base.Verify.verify(ZLjava/lang/String;Ljava/lang/Object;)V 19:52:50 at com.google.errorprone.ErrorProneAnalyzer.finished(ErrorProneAnalyzer.java:124) 19:52:50 at jdk.compiler/com.sun.tools.javac.api.MultiTaskListener.finished(MultiTaskListener.java:132) 19:52:50 at jdk.compiler/com.sun.tools.javac.main.JavaCompiler.flow(JavaCompiler.java:1418) 19:52:50 at jdk.compiler/com.sun.tools.javac.main.JavaCompiler.flow(JavaCompiler.java:1365) 19:52:50 at jdk.compiler/com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:960) 19:52:50 at jdk.compiler/com.sun.tools.javac.api.JavacTaskImpl.lambda$doCall$0(JavacTaskImpl.java:104) 19:52:50 at jdk.compiler/com.sun.tools.javac.api.JavacTaskImpl.handleExceptions(JavacTaskImpl.java:147) 19:52:50 at jdk.compiler/com.sun.tools.javac.api.JavacTaskImpl.doCall(JavacTaskImpl.java:100) 19:52:50 at jdk.compiler/com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:94) 19:52:50 at org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess(JavaxToolsCompiler.java:126) 19:52:50 at org.codehaus.plexus.compiler.javac.JavacCompiler.performCompile(JavacCompiler.java:174) 19:52:50 at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:1129) 19:52:50 at org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:188) 19:52:50 at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137) 19:52:50 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) 19:52:50 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154) 19:52:50 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146) 19:52:50 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117) 19:52:50 at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:200) 19:52:50 at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:196) 19:52:50 at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) 19:52:50 at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) 19:52:50 at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) 19:52:50 at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) 19:52:50 at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) 19:52:50 at java.base/java.lang.Thread.run(Thread.java:834) 19:52:50 [INFO] ------------------------------------------------------------- 19:52:50 [ERROR] COMPILATION ERROR : 19:52:50 [INFO] ------------------------------------------------------------- 19:52:50 [ERROR] An unknown compilation problem occurred 19:52:50 [INFO] 1 error

while this is not a bug per se - it would be nice if the two projects could align on a common guava version or work-around so that both processors could be used at the same time.

Environment

None

Activity

Marko BekhtaDecember 10, 2024 at 2:54 PM

I'm going to close this one since `hibernate-validator-annotation-processor` does not have Guava in test dependencies anymore. If there are still problems with the annotation processor, please open a new ticket; thanks!

Gunnar MorlingNovember 13, 2018 at 7:10 PM

Hum, hum, we only use Guava as a test dependency, so I'm wondering where this is coming from. Can you share a (minimal POM) which exposes this issue so we can reproduce it? Thanks! Long time, no type, btw

DavidKNovember 13, 2018 at 7:00 PM

Out of Date

Details

Assignee

Reporter

Labels

Bug Testcase Reminder (view)

Bug reports should generally be accompanied by a test case!

Bug Testcase Reminder (edit)

Bug reports should generally be accompanied by a test case!

Participants

DavidK
Gunnar Morling
Marko Bekhta

Components

Affects versions

Priority

Created November 13, 2018 at 6:57 PM
Updated December 10, 2024 at 2:54 PM
Resolved December 10, 2024 at 2:54 PM