[ 
https://issues.apache.org/jira/browse/CAMEL-23999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18095359#comment-18095359
 ] 

Federico Mariani commented on CAMEL-23999:
------------------------------------------

PR: https://github.com/apache/camel-spring-boot/pull/1843

_Claude Code on behalf of Federico Mariani._

> camel-spring-boot - Jars no longer contain spring-configuration-metadata.json 
> after maven-compiler-plugin 3.15.0 upgrade
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-23999
>                 URL: https://issues.apache.org/jira/browse/CAMEL-23999
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-spring-boot
>            Reporter: Federico Mariani
>            Assignee: Federico Mariani
>            Priority: Major
>             Fix For: 4.22.0
>
>
> The maven-compiler-plugin upgrade to 3.15.0 in camel-spring-boot (dependabot 
> PR #1648) silently stopped running annotation processors discovered on the 
> compile classpath (behaviour change introduced in maven-compiler-plugin 
> 3.13+, which requires {{<proc>}} to be configured explicitly).
> As a result, {{spring-boot-configuration-processor}} no longer runs, and the 
> {{camel-spring-boot}} core jar and *all* starter jars are built without 
> {{META-INF/spring-configuration-metadata.json}}. Verified by building 
> {{core/camel-spring-boot}} and {{camel-mock-starter}} from current main and 
> listing the jar contents: no metadata file is present.
> Impact:
> * No IDE auto-completion/documentation for any {{camel.*}} configuration 
> property for applications using 4.22.0-SNAPSHOT builds.
> * The generated property documentation ({{src/main/docs/*.json}}, e.g. 
> {{spring-boot.json}}) can no longer be regenerated, since the update mojos 
> copy the annotation-processor output.
> Fix: configure {{<proc>full</proc>}} on maven-compiler-plugin in the root pom 
> so processor execution is restored for all modules.
> _Reported and fixed by Claude Code on behalf of Federico Mariani._



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to