smongiar opened a new pull request, #134:
URL: https://github.com/apache/camel-upgrade-recipes/pull/134
## Problem
`UpgradeDependencyVersion` resolves the target version from
`maven-metadata.xml`. When that file is absent from the repository (e.g.
staging or mirror repos that do not publish metadata), the recipe silently
no-ops on a property reference such as `${camel-spring-boot-version}` — the BOM
version is left unchanged.
## Fix
Add companion `ChangePropertyValue` entries that set the property value
directly, without requiring metadata resolution:
- `camel-spring-boot-version`: property name used by
`camel-spring-boot-examples`
- `camel.springboot.version`: alternate property name variant
- `spring-boot-version`: Spring Boot version property
The existing `UpgradeDependencyVersion` entries are **preserved** to handle
the literal-version case (where there is no property to update).
Also removes a duplicate `UpgradeDependencyVersion` entry for
`camel-spring-boot-dependencies` that was present twice in the recipe list.
## Changes
- `latest.yaml`: add three `ChangePropertyValue` entries alongside the
existing `UpgradeDependencyVersion` entries
- `CamelSpringBootBomVersionTest`: new regression test covering all three
shapes:
- Property-managed BOM via `${camel-spring-boot-version}`
- Property-managed BOM via `${camel.springboot.version}`
- Literal-version BOM (existing `UpgradeDependencyVersion` path, confirmed
still works)
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
