JiriOndrusek opened a new issue, #138: URL: https://github.com/apache/camel-upgrade-recipes/issues/138
`camel-spring-boot-upgrade-recipes/pom.xml` hardcodes versions that Spring Boot already manages: ```xml <springframework-version>7.0.10</springframework-version> <spring-security-version>7.1.2</spring-security-version> <spring-batch-version>6.0.6</spring-batch-version> ``` They are filtered into `spring-framework-6-to-7.yaml`, `spring-security-6-to-7.yaml` and `spring-batch-5-to-6.yaml`. When `spring-boot-version` is bumped, the others are easy to forget, so recipes may set versions not matching that Spring Boot. Same for the 4.18 LTS pair (`spring-boot-4.18-lts-version` / `springframework-4.18-lts-version`). **Proposal** Keep only `spring-boot-version` and derive the rest from `spring-boot-dependencies` (`spring-framework.version`, `spring-security.version`, `spring-batch.version`) at build time, e.g. a small build step reading the BOM. If that's too much, at least add a build/test check that fails when the values differ from the BOM. -- 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]
