[
https://issues.apache.org/jira/browse/MNG-8491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet closed MNG-8491.
--------------------------------
Resolution: Won't Fix
I'll close this one as won't fix.
I think it started with a misunderstanding about changes in the JDK: the change
is not about how annotation processors are discovered, but the fact that
annotation processing is disabled by default in JDK 22. "implicit annotation
processing" refers to the fact that the default behavior of the javac compiler
was to launch annotation processing with discovered processors by default.
This has changed in JDK 22, but the discovery mechanism is not modified.
[~kwin] feel free to chime in if you disagree
> 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)
