[
https://issues.apache.org/jira/browse/MNG-8491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17910391#comment-17910391
]
Guillaume Nodet commented on MNG-8491:
--------------------------------------
This is in no way specific to this artifact. This is a generic problem which
affects all annotation processors. What you suggest is basically to remove all
automatic configuration of annotation processors. The mentioned problem is a
generic one (i.e. a malicious transitive dependency) which cannot happen here
since we do control our own dependencies.
So in this very case, this will make user's life harder for no benefit.
I'd really rather try to find a way to fix the problem rather than removing the
feature.
> 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)
