We have used kotlin scripting for creating a dsl o...

# scripting

[Ashish Sharma]

We have used kotlin scripting for creating a dsl over healthcare events in our Health Record System. This is what we do:
1. We have a set of predefined scripts. We compile these into a jar and load it at startup of our application.
2. Users can define overrides for our DSL, b creating a DSL file annotate with a @file annotation which overrides that dsl name.
3. In certain cases, we would like to debug through the scripts we have compiled as jars (and which are loaded at startup)
How can we step into a script while debugging which is compiled into a jar and loaded using a URL class loader at startup? We are able to invoke the script and get the result, but we are not able to step into the code using the attached debugger.
The main reason for compiling scripts upfront into a jar is that we are facing a lot of delay on compiling scripts at startup using the scripting host. We have around 100 scripts with 100-150 lines each.

[ilya.chernikov]

In general it should be the same as with other, non-script files. I'm usually able to step into scripts or put breakpoints there, if IntelliJ "sees" the script somewhere in the project sources.