RFR: JDK-8306819: Consider disabling the compiler's default active annotation processing

[Josiah Noel]

Is it really such a common thing that people accidentally include unrelated
annotation processor dependencies transitively via maven? Most of the time,
I see processors are explicitly defined with the provided or optional scope
meaning they aren't usually pulled transitively. Perhaps the most used
annotation processor Lombok (even though it breaks the rules, it starts
with annotation processing) tells it's users to add it via provided scope.


On Sun, Sep 10, 2023, 8:58 AM altrisi <duke at openjdk.org> wrote:

> On Mon, 12 Jun 2023 23:49:51 GMT, Joe Darcy <darcy at openjdk.org> wrote:
>
> > Change annotation processing to be opt-in rather than opt-out.
>
> This doesn't remove annotation processors, just disables them running by
> default with no input from the developer (I assume if they were simply in
> the compiler classpath, which could happen by accident). As mentioned, it
> can still be enabled by its flag, and it's likely build systems will set
> that flag for you if you have declared you use annotation processors for
> your build.
>
> I also disagree in the hardly used anymore part though, but I have no data.
>
> -------------
>
> PR Comment: https://git.openjdk.org/jdk/pull/14432#issuecomment-1712807240
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/compiler-dev/attachments/20230910/db1b9a49/attachment.htm>