[Bug] Annotation processor generated duplicated classes from dependency that also used autovalue about auto HOT 3 OPEN

This vaguely reminds me my 9-year-old blog post: https://blog.ltgt.net/most-build-tools-misuse-javac/

Could it be that the Apache Beam sources are present in the compile class path? Javac could then possibly compile them and thus process them, but there likely is a workaround.

from auto.

Could it be that the Apache Beam sources are present in the compile class path

Apache Beam jar (compiled .class) is present in compile class path, though the source code does not.

Current workaround is to duplicate the affected Beam sources into the project, so autovalue still generate duplicated class but with correct nullness handling

from auto.

There are in fact source files in the Apache Beam jar: beam-jar-source-files.txt. I don't know if that is the source of the problem, though. It doesn't look as if any of the sources contain @AutoValue classes.

from auto.