+1, very cool idea. A proper review of the code might be in order.

On a quick review of the code, and given that we're populating the
class loader of current thread, can we ensure clean termination of
shells?

On Sat, Jan 12, 2019 at 9:14 PM Mathieu Lirzin
<mathieu.lir...@nereide.fr> wrote:
>
> Hello,
>
> One issue with the current way of writing Groovy tests is that the
> feedback between writing an instruction and checking its result is slow
> because one has to rerun the corresponding test case.
>
> Providing a Groovy shell access with a delegator and dispatcher allows
> developers to interactively execute commands and check their results
> instantly.
>
> I have implemented such feature in OFBIZ-10805 [1] which might be
> interested to follow/review for those who care about interactive
> development.
>
> Thanks.
>
> [1] https://issues.apache.org/jira/browse/OFBIZ-10805
>
> --
> Mathieu Lirzin
> GPG: F2A3 8D7E EB2B 6640 5761  070D 0ADE E100 9460 4D37

Reply via email to