Building projects using ADK should not show the confusing message about Annotation processing is enabled because ...

[vorburger]

Describe the bug
A clear and concise description of what the bug is.

$ git clone https://github.com/enola-dev/LearningADK.git
$ cd quickstart
$ ../mvnw clean compile

(...)

[INFO] --- compiler:3.14.0:compile (default-compile) @ adk-agents ---
[INFO] Recompiling the module because of changed source code.
[INFO] Compiling 1 source file with javac [debug target 21] to target/classes
[INFO] Annotation processing is enabled because one or more processors were found
  on the class path. A future release of javac may disable annotation processing
  unless at least one processor is specified by name (-processor), or a search
  path is specified (--processor-path, --processor-module-path), or annotation
  processing is enabled explicitly (-proc:only, -proc:full).
  Use -Xlint:-options to suppress this message.
  Use -proc:none to disable annotation processing.

This doesn't really cause any harm, but it's... still at least a bit "surprising", no?

I wonder what JAR pulls along an (unused, clearly) APT, and how we might exclude it.

@glaforge FYI

[glaforge]

Isn't it AutoValue?

[vorburger]

Isn't it AutoValue?

Ah yeah, you're probably right! But this is a Maven POM bug (in this project, not Auto), because:

While the AutoValue annotation JAR may well be a transitive dependency, the APT processor's artifact itself should not be, of course.

#178 will fix this.

[vorburger]

Fixed by #178.