Re: [PR] Mark modules using legacy @ConfigRoot as such [camel-quarkus]

2024-08-09 Thread via GitHub
jamesnetherton commented on PR #6331: URL: https://github.com/apache/camel-quarkus/pull/6331#issuecomment-2277291714 Thanks @gsmet! I can follow up with any additional tweaks. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to G

Re: [PR] Mark modules using legacy @ConfigRoot as such [camel-quarkus]

2024-08-09 Thread via GitHub
jamesnetherton merged PR #6331: URL: https://github.com/apache/camel-quarkus/pull/6331 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr.

Re: [PR] Mark modules using legacy @ConfigRoot as such [camel-quarkus]

2024-08-08 Thread via GitHub
gsmet commented on PR #6331: URL: https://github.com/apache/camel-quarkus/pull/6331#issuecomment-2276402031 I added more details here: https://github.com/quarkusio/quarkus/wiki/Migration-Guide-3.14#extension-developers Note that by applying just this patch, you will get a warning when

Re: [PR] Mark modules using legacy @ConfigRoot as such [camel-quarkus]

2024-08-08 Thread via GitHub
gsmet commented on PR #6331: URL: https://github.com/apache/camel-quarkus/pull/6331#issuecomment-2276373479 At your disposal if you have any questions about this change! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use

[PR] Mark modules using legacy @ConfigRoot as such [camel-quarkus]

2024-08-08 Thread via GitHub
gsmet opened a new pull request, #6331: URL: https://github.com/apache/camel-quarkus/pull/6331 The new extension annotation processor coming with 3.14 requires that you mark the modules using the legacy @ConfigRoot approach (i.e. without @ConfigMapping) with a specific annotation processor