You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problems with UpgradeParentPomVersion and jakarta classifier
The petclinic defines a ehcache dependency.
This dependency requires a jakarta classifier in 3.0.
Attempts to bump the parent version of the
pom.xml from petclinic from 2.7.1 to 3.0.0-M3 using UpgradeParentPomVersion failed. But the recipe was printed as successful applied.
Another problem was that the parent version wasn't updated (and exception swallowed) to 3.0.0-M3 without previously adding the jakarta classifier to the ehcache dependency.
But adding the jakarta classifier alone in 2.7 made the dependency resolution fail because the version managed by Spring Boot 2.7 does not exist with jakarta classifier.
Adding classifier and the version used in Boot 3.0.0 to the ehcache dependency in 2.7 and removing the version after bumping the parent to 3.0.0 solves this. This will probably be the case for more dependencies.
The text was updated successfully, but these errors were encountered:
fabapp2
changed the title
3.0.0: Run dependency upgrades before bumping parent version
3.0.0: Problems when upgrading spring petclinic to boot 3
Aug 5, 2022
Testing the upgrade recipe to Spring Boot 3.0.0-M3 with the spring petclinic surfaced problems.
Printout of applied actions
The console prints all actions of a recipe as applied, regardless of their condition, see
Problems with
UpgradeParentPomVersion
andjakarta
classifierThe petclinic defines a
ehcache
dependency.This dependency requires a
jakarta
classifier in 3.0.Attempts to bump the parent version of the
pom.xml from petclinic from 2.7.1 to 3.0.0-M3 using
UpgradeParentPomVersion
failed. But the recipe was printed as successful applied.OpenRewriteRewriteRecipeAdapter
s #287Another problem was that the parent version wasn't updated (and exception swallowed) to 3.0.0-M3 without previously adding the
jakarta
classifier to theehcache
dependency.But adding the
jakarta
classifier alone in 2.7 made the dependency resolution fail because the version managed by Spring Boot 2.7 does not exist withjakarta
classifier.Adding classifier and the version used in Boot 3.0.0 to the
ehcache
dependency in 2.7 and removing the version after bumping the parent to 3.0.0 solves this. This will probably be the case for more dependencies.@pway99👆
The text was updated successfully, but these errors were encountered: