Generate OpenRewrite recipes with JavaParser.Builder#classpathFromResources

[timtebeek]

Add a annotation processor argument to switch to classpath from resource for the generated OpenRewrite recipes:
https://github.com/openrewrite/rewrite-templating/?tab=readme-ov-file#use-javaparserbuilder-classpathfromresourcesctx-guava-31

By default, the annotation processor will use JavaParser.runtimeClasspath() to resolve the classpath for newly generated Java code snippets. If you want to use TypeTables from src/main/resources/META-INF/rewrite/classpath.tsv.gz instead, pass in: -Arewrite.javaParserClasspathFrom=resources.

Right now we're having to replicate the provided dependencies in EPS in rewrite-third-party to get the recipes to work at all, and even then they do not work well in all environments. By switching to type tables we only need to capture the public APIs of the dependencies, for a much smaller and safer runtime.

Follows

• Upgrade OpenRewrite 3.14.0 -> 3.16.0 #1853
• Use classpathFromResources in recipes generated for Refaster rules openrewrite/rewrite-templating#139
• Add additional jar names to classpathFromResources for types referenced from types used openrewrite/rewrite-templating#160

[github-actions]

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

[github-actions]

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

[timtebeek]

[WARNING] The following options were not recognized by any processor: '[rewrite.javaParserClasspathFrom]'

Which is odd, since I'm explicitly setting that as supported option here: 🤔
https://github.com/openrewrite/rewrite-templating/blob/a869184ed27513bebec66d4b9e9d9adb7899425b/src/main/java/org/openrewrite/java/template/processor/RefasterTemplateProcessor.java#L48-L56

[Stephan202]

The issue manifested only with JDK 25. I rebased and added a commit to move the config to the proper location. But now there's another error you may want to look at. (I just did this in between meetings; can circle back later.)

[timtebeek]

Thanks yes can confirm; I think it's because over here we use a lib for the annotations, whereas in our tests we had those inlined. Ought to be fixed with a small adjustment to the template processor and a new release.

[github-actions]

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

[github-actions]

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

[github-actions]

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

[github-actions]

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

[Stephan202]

Nice! I added one commit. I checked the generated code; LGTM.

Suggested commit message:

Generate OpenRewrite recipes with `JavaParser.Builder#classpathFromResources` (#1918)

[github-actions]

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

[github-actions]

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

[timtebeek]

Any concerns here @rickie ? Would love to get this in to make the corresponding changes on our end.

[Stephan202]

❗ @rickie let's merge #1932 first. ❗

[github-actions]

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.