Ability to debug Build.kt script

Actually ability to debug Build.kt file (not only Kobalt internals like Manifest.attributes) will be a great feature. User can have some fun complexMethod inside Build.kt and debug it. The problem why it is not working at the moment is the way like Kobalt compile Build.kt file. It saves to temporary dir with some random kobalt-XXXXX.kt name and compile it and pack inside buildScript.jar. The result classes will be the following:

But the original source file still Build.kt and debug doesn’t catch it.

It should use exactly Build.kt source file to make debug possible. Kobalt should compile and pack into buildScript.jar the actual Build.kt file, so the resulting jar will be the following:

@cbeust Any thoughts how to avoid compile and packaging temporary sources?

[cbeust]

Ah I see.

I think there was a reason why I decided to copy Build.kt in a temporary directory and compile that one instead of the original one but I can’t remember why. Maybe some locking issue.

I’ll make the change you suggested, we’ll see how it goes.

[dmitry-zhuravlev]

It is really cool to debug almost all code in Build.kt. It’s killer feature 😃