Resolve hang in failure scenario

[cab105]

Experienced a hang while attempting to use the spring-boot-migrator to convert a Mule project to Spring Boot. Tracing the hang resulted in a failure occurring within the program itself, and rather than indicating the failure, spring-boot-migrator locked itself into an infinite loop where issuing a SIGINT from the console wasn't enough.

This fix converts the while check to an if check to ensure that the failure message gets printed, and the program can return a prompt.

[sanagaraj-pivotal]

Hello @cab105 welcome to Spring-boot-migrator team, we recently had a stab at solving this issue with one of our open rewrite based recipes.

Could you provide us a sample small mule project that exhibits this behaviour? or try latest SBM on your sample

[fabapp2]

Thanks @cab105 🚀

I am sorry you had to dig into this area of the code ;)
As @sanagaraj-pivotal wrote, an example project would be great?
Nevertheless, I merged it.

[cab105]

Thank you @fabapp2 and @sanagaraj-pivotal.

For context this is against the latest source tree, and with this "fix" in place, I'm able to get a proper failure scenario with stacktrace using stacktrace from the CLI. I am seeing the following error being thrown:
Caused by: java.lang.IndexOutOfBoundsException: Index 0 out of bounds for length 0 this is occurring at

spring-boot-migrator/components/sbm-recipes-mule-to-boot/src/main/java/org/springframework/sbm/mule/actions/JavaDSLAction2.java

Line 191 in 5d51df2

JavaSourceSet mainJavaSourceSet = projectContext.getApplicationModules().getTopmostApplicationModules().get(0).getMainJavaSourceSet();

.

I'm still digging into the underlying failure to determine why it isn't locating the application context as this is blocking the other PR I'm working on.

As to the sample that I've been using for my own development/testing, it is this:
https://gist.github.com/cab105/be696eca9380b751219f6395febf6afb