[refactoring] running Spring Boot 3 open-rewrite migration recipes takes very long

[martinlippert]

Using the standard petclinic example and running the "upgrade to Spring Boot 3" recipe takes very very long. We need to improve this. A few thoughts here:

• maybe not use a modal dialog? (this feels very old school and you cannot do anything anymore in between, but not sure about the consequences)
• does open-rewrite resolve the maven project from scratch again? If so, can we skip that step somehow and tell open-rewrite that we have the resolved classpath of the project already to speed things up?

[martinlippert]

In case we can't speed things up, we should at least have a meaningful progress message that tells the user what is going on that the moment behind the scenes and which step exactly takes a long time at the moment (parsing, downloading dependencies, whatever)

[BoykoAlex]

I pass list of JARs to the Maven Project parser but still calculates dependencies without downloading them. I'll double-check if there is anything i can do to speed this up.
The progress used to state which stage it was on (still does in VSCode). I have switched to lsp4e handling of progress messages and now the stage progress messages are gone. I can look into reanimating specific stage messages.

[martinlippert]

This is probably not the highest priority at the moment, but we should take a look into this to find out what is causing the performance issue.

It felt to me like the first time I executed this recipe it was super slow, but the performance improved over time - for whatever reason. Let's investigate why this was slow (I can take a look into this and play around with it a bit) - nothing you need to tackle immediately I would say.

[BoykoAlex]

Rewrite downloads dependencies POM's (probably metadata as well). This seem to take time. The POM's (and other files) are in the local maven repo - we need to find a way to take advantage of this fact.

[martinlippert]

Something to further investigate in the 4.17.1 release cycle.