Druid: IntelliJ Annotation processor prevents running tests in IntelliJ

[drcrallen]

When I try to run tests from IntelliJ I'm getting the following error:

Error:java: Annotation processor 'io.druid.annotations.SubclassesMustBePublicAnnotationProcessor' not found

Running mvn test works fine.

[jihoonson]

Interesting. I've never met this error before.

[gianm]

I haven't hit it either. I am using IDEA 2018.1.

I think @clintropolis has hit something similar though.

[leventov]

I started to have this recently, too. Something broke in intellij.

[clintropolis]

My crummy workaround for now is to delete .idea/compiler.xml, but haven't determined the cause.

[leventov]

https://youtrack.jetbrains.com/issue/IDEA-193368

[himanshug]

I had hit it recently . I think the problem is not in the Intellij but the maven-compiler-plugin version getting used which is determined from https://search.maven.org/remotecontent?filepath=io/druid/oss-parent/2/oss-parent-2.pom to be 3.2 while configuration "annotationProcessorPaths" was introduced in version 3.5 ( see https://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html ) which is why it is not recognized. For example manually overriding the version to 3.7 in druid-processing pom solves the problem.
we need to update the version of maven-compiler-plugin to at least 3.5 .

[leventov]

Why would not we update the version of maven-compiler-plugin project-wide?

[leventov]

@himanshug your suggestion didn't help me, I still get this build error.

[leventov]

This issue is presumably already fixed in IntelliJ 2018.2 EAP: https://youtrack.jetbrains.com/issue/IDEA-188940

[josephglanville]

Tests run for me using IDEA Ultimate 2018.2 EAP from Toolbox.

[himanshug]

@leventov

Why would not we update the version of maven-compiler-plugin project-wide?

if version upgrade fixed the problem then we would update in the common place unless there was a problem , why maintain different version in different poms unless necessary.

but anyways, it version update doesn't fix it so not necessary but I'm curious how it works with 3.2 when that configuration didn't exist there.

[drcrallen]

Confirmed fixed in the EAP

[leventov]

Closing this issue because IntelliJ 2018.2 with a fix is released

[asdf2014]

I also confirmed that after upgrading Intellij Idea to v2018.2, it no longer happens. Thanks all.