Dmitry Zhuravlev

What do you mean by "opening a project with no Kobalt files"?

ping @cbeust Any thoughts about it?

Thanks! I'll take a look and implement hierarchy in the plugin. However I found some maybe bug: If I specify `dependencies { provided("...") runtime("...") }` It still sended in DependencyData.scope...

I think it is not so trivial because `IClasspathDependency` knows nothing about the scope. And one of the implementations like `AetherDependency` should be extended to incapsulate the scope. @cbeust Maybe...

`DependencyData` have only hardcoded `compile` like described here: https://github.com/cbeust/kobalt/blob/master/src/main/kotlin/com/beust/kobalt/app/remote/DependencyData.kt#L68-L71 So to eliminate this hardcode we need to get the scope from some other place...

@cbeust Not so easy: plugin implementation should be compatible with Android Studio. I already found some compilation mistmatch and fixed in the new "android_studio" branch. However it seems that Android...

Another problem that comments doesn't properly handled in Build.kt: Try specify this: ``` /*val build = buildScript{ repos("dl.bintray.com/cbeust/maven") plugins("com.beust:kobalt-line-count:0.5") }*/ val bs = buildScript { repos("bintray.com/kotlin/kotlin-eap-1.1") plugins("com.beust.kobalt:kobalt-line-count:0.18") } ``` In...

Great! I'll investigate this more deeply.

Added web socket support to plugin. Now all messages like > Synchronizing > project kobalt-wrapper 1/3 > Synchronizing project kobalt-plugin-api 2/3 > Synchronizing project kobalt 3/3 > Received dependency data:...

Yep, it is sufficient for java compiler. But maybe we need additional `jdkVersion` flag? In the most cases `jdkVersion`=`languageLevel`=`source compiler flag` but there is some use cases in which the...