Skip to content

3.0.0: Problems when upgrading spring petclinic to boot 3 #294

@fabapp2

Description

@fabapp2

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 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.

@pway99👆

  • [ ]

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions