Groovysh entry point with binding injection for embedding #2364
+60
−5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Background
As part of the ongoing effort to upgrade Grails to Groovy 5, it became apparent that the
Groovyshclass is no longer available. It was replaced by theMainclass when Groovy switched to JLine 3 (introduced in #2263).Current Situation
Grails currently relies on
Groovyshto start an interactive shell with a preconfiguredBinding, for example:This approach allows Grails to inject application-specific context into the shell.
Problem
The new
Mainclass does not provide a programmatic entry point that allows callers to supply a customBinding. As a result, there is no straightforward way to replicate the existing Grails behavior using the new shell infrastructure.Proposed Solution
This PR introduces a programmatic entry point to the
Mainclass that makes it possible to inject aBinding. This restores the ability for Grails (and other consumers) to launch the Groovy shell with a predefined execution context, preserving existing functionality while remaining compatible with Groovy 5.