[
https://issues.apache.org/jira/browse/MNG-8491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17910396#comment-17910396
]
Guillaume Nodet commented on MNG-8491:
--------------------------------------
More references:
* https://github.com/openjdk/jdk/pull/14432
* https://github.com/openjdk/jdk/pull/14499
Those threads explicitly mention Maven.
The problem is really about *implicit* annotation processing. If the user has
explicitly requested annotation processing, he becomes responsible for the
annotation processors used.
That's why I really suggest looking at fixing the problem where it happens,
i.e. where the annotation processsing is configured, i.e. in
maven-compiler-plugin.
I think the problem is really in transitive third party dependencies. Would
m-compiler-p scan the direct dependencies, the problem is no more one.
> Make DIIndexProcessor opt-in
> ----------------------------
>
> Key: MNG-8491
> URL: https://issues.apache.org/jira/browse/MNG-8491
> Project: Maven
> Issue Type: Improvement
> Components: API
> Affects Versions: 4.0.0-rc-2
> Reporter: Konrad Windszus
> Priority: Blocker
>
> Currently the DIIndexProcessor is automatically registered in
> https://github.com/apache/maven/blob/master/api/maven-api-di/src/main/resources/META-INF/services/javax.annotation.processing.Processor.
> This should be removed as it may lead to surprising effects and is no longer
> recommended by Oracle. Also since Java 22+ implicit annotation processors are
> no longer considered (https://bugs.openjdk.org/browse/JDK-8306819) and need
> to be explicitly configured.
> To streamline the behaviour for consumers among all supported Java versions
> we should get rid of automatic annotation processor registration and document
> how to opt-in.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
