You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After the plugin has been applied, you can run the `downloadRecipeDependencies` task. This will download the corresponding jar for every dependency specified in `recipeDependencies` and put them in the `src/main/resources/META-INF/rewrite` directory. From there, you could use the `classpathFromResources` function in the same way as above.
Ideally we call out the new task first, before indicating that there's an older way to so things as well.
TypeTables are a potential replacement in most cases, with only some known limitations where it concerns meta annotations right now.
What problem are you trying to solve?
Document the new
./gradlew createTypeTable
task as a suggested replacement for./gradlew downloadRecipeDependencies
.Describe the solution you'd like
Right now we document the old task here:
rewrite-docs/docs/authoring-recipes/multiple-versions.md
Line 56 in 7e160db
Ideally we call out the new task first, before indicating that there's an older way to so things as well.
TypeTables are a potential replacement in most cases, with only some known limitations where it concerns meta annotations right now.
There's also a FAQ entry that could use an update to call out TypeTable as we potential solution:
https://docs.openrewrite.org/reference/faq#why-do-artifact-scanners-detect-vulnerabilities-in-recipe-artifactsjars
Have you considered any alternatives or workarounds?
Seems too early to fully remove packaged recipe jars.
Additional context
TypeTable
as a substitute for packing whole jars intoMETA-INF/rewrite/classpath
rewrite#4932The text was updated successfully, but these errors were encountered: