-
Hi team, Let's say I have a complex Spring Boot project that I would like to migrate to Spring Boot 2.7 or Spring Boot 3, but I don't want to migrate from Is there a way to activate a recipe and define sub-recipe(s) that we'd like to ignore, like the following ?
Thanks, |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Hi @adriil ; There's not currently a way to exclude certain recipes, as it get's complicated quickly with the way recipes chain one another, and the assumptions they each build upon in having the code in a certain state. That said, for your particular use case here it sounds like you'd be interested in the work started in openrewrite/rewrite-spring#351 ; there we're considering having separate recipes that decouple the spring migrations from one another, such that you can run the individual spring minor version migrations without getting the chained junit 5 migration with each. Would that help you through here? As a side note: I think Spring Boot 3 dropped support for JUnit 4, at least for the spring specific test constructs. Up until Spring Boot 2.7 you can still get away with the junit vintage runner I believe, so you might get stuck at 2.7 with vintage runner for JUnit 4. Ultimately we do recommend you upgrade fully to JUnit 5; let us know if you're missing specific functionality to migrate fully. |
Beta Was this translation helpful? Give feedback.
Hi @adriil ; There's not currently a way to exclude certain recipes, as it get's complicated quickly with the way recipes chain one another, and the assumptions they each build upon in having the code in a certain state.
That said, for your particular use case here it sounds like you'd be interested in the work started in openrewrite/rewrite-spring#351 ; there we're considering having separate recipes that decouple the spring migrations from one another, such that you can run the individual spring minor version migrations without getting the chained junit 5 migration with each. Would that help you through here?
As a side note: I think Spring Boot 3 dropped support for JUnit 4, at least fo…