Marcin Kuszczak

For completeness: with version 0.6.2 I get the following error (see below). This time it is caused by: Caused by: com.android.tools.r8.utils.AbortException: Error: **MethodHandle.invoke** and **MethodHandle.invokeExact** are only supported starting with...

@ligee, @ileasile - as I have mentioned in [#Kotlin/KEEP](https://github.com/Kotlin/KEEP/issues/75), I have an initial implementation of support for Kotlin Scripting in kscript. Those files are mostly a copy of Kotlin Scripting...

I have renamed the branch to kscript_4.5 - it's too early to release Kotlin Scripting in the next version. https://github.com/kscripting/kscript/tree/kscript_4.5

I am not really convinced that referring to local files from annotation DependsOn is the right way of solving the need to use local jars. First of all, I don't...

@holgerbrandl , @vsajip - after rethinking KSCRIPT_LOCAL_JAR_DIRECTORY concept presented by me above, I also agree that it won't be the best way to go. But please let me propose another...

Nope. The flow should be like that: ` export KSCRIPT_LOCAL_JARS=/home/myjars/myjar1.jar;/home/myjars/myjar2.jar ` Then in ConfigBuilder, if the env variable is set, it should be parsed, changed to the list of OsPath,...

Ok, I will reopen the ticket then. After I make some additional refactoring on kscript, I will look at the implementation.

Ok. Then I will work on migration to the new organization in the next iteration. (I have just created kotlin-scripting organization; you are invited) In the meantime can you please...

Thanks for the report! The issue is already fixed in the master branch. @holgerbrandl - can you please release the new version from the master? Unfortunately, I have no capacity...

@christianitis - as a workaround you can edit kscript shell script: `current line 49: eval "exec $("${KOTLIN_BIN}kotlin" -classpath "${JAR_PATH}" kscript.app.KscriptKt "$OSTYPE" "$@")" modify it into: eval "exec $("${KOTLIN_BIN}kotlin" -classpath "${JAR_PATH}"...