Fix LogManager logger call chain

[gdupontf]

What's changed?

This produces the proper method chain to obtain a logger using JUL.

What's your motivation?

Simple bugfix.

Anything in particular you'd like reviewers to focus on?

I didn't change much, but a local build couldn't pass the two license tasks and a few tests just failed on some snakeyaml problems. But the scope of the changes is far from affecting anything there.

Anyone you would like to review specifically?

Have you considered any alternatives or workarounds?

N/A

Any additional context

Unless you want a specific test that checks that code compiles there's not much to change or add of value in tests.

Checklist

• I've added unit tests to cover both positive and negative cases
• I've read and applied the recipe conventions and best practices
• I've used the IntelliJ IDEA auto-formatter on affected files

[github-actions]

Some suggestions could not be made:

• src/main/java/org/openrewrite/java/logging/log4j/LoggingExceptionConcatenation.java
  • lines 1-0
• src/test/java/org/openrewrite/java/logging/log4j/LoggingExceptionConcatenationTest.java
  • lines 1-1
  • lines 18-17

[timtebeek]

Thanks a lot! I'll get those suggestions sorted and see this through tomorrow.

[timtebeek]

Great to have you on board! Really helpful to have this issue fixed, and thanks for taking on the extra work too.