[
https://issues.apache.org/jira/browse/MNG-8491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17910445#comment-17910445
]
Guillaume Nodet commented on MNG-8491:
--------------------------------------
Sure, that's a valid use case.
But one can configure explicitly the annotation processors wanted if the
default discovery process is not suited to that use case.
IIUC, what you suggest is to force user to declare annotation processors, which
is already doable, so not sure why we'd remove the possibility for automatic
discovery. I haven't seen any reference in the JDK changes to removing that.
Simply to not make if the default anymore AFAIK.
> 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)
