[
https://issues.apache.org/jira/browse/CAMEL-23376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18113922#comment-18113922
]
Guillaume Nodet commented on CAMEL-23376:
-----------------------------------------
This issue is being investigated by a coding agent (on behalf of gnodet).
Analysis: The root cause is that maven-release-plugin preparationGoals runs
"clean install" but does not regenerate the generated metadata files (in
src/generated/ directories) that embed the version. After the SNAPSHOT bump,
those generated files still contain the old version. The fix is to add a
completionGoals configuration to the maven-release-plugin in the root pom.xml
to run regeneration (e.g., "-Pregen install") after the development version is
set. The release guide (docs/user-manual/modules/ROOT/pages/release-guide.adoc)
should also be updated accordingly.
_Note: This comment was generated by an AI coding agent and requires manual
verification._
> Add a refresh commit to the release process
> -------------------------------------------
>
> Key: CAMEL-23376
> URL: https://issues.apache.org/jira/browse/CAMEL-23376
> Project: Camel
> Issue Type: Task
> Components: build system
> Reporter: Thomas Cunningham
> Assignee: Guillaume Nodet
> Priority: Minor
>
> Would it be possible to add a refresh commit as part of the release process
> after the new SNAPSHOT version is set?
> I've noticed on camel and camel-spring-boot that the release process does a
> versions:set that bumps the versions to the next SNAPSHOT but we always need
> to submit a refresh PR afterwards so that all the json and properties files
> get regenerated with the new -SNAPSHOT version.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
