Dmitry Zhuravlev

E.g. it could be some boolean flag in `Dependencies.compile(export=true)` And not only for compile (compile, test, runtime, provided). Kobalt server should send this flag together with all dependencies. And I'll...

It is simple: user just specified it in the `Build.kt` e.g.: `dependencies { compile("com.google.inject:guice:4.0", exported=true) }`

"I can't think of a situation when you'd ever want a dependency not imported." Maybe the case is when user want to use some other version of library in the...

Also the main cons against "export" is because it not so obvious. So you cannot just open the module structure and see all dependencies. You see only one dependency and...

@cbeust I think we should deprecate './kobaltw --init idea' because it generates some "old" format not suited for the new plugin. This functionality fully integrated within plugin during "import\create project"....

Just for fun I tried to do --init idea and got NPE on Windows: java -Dfile.encoding=windows-1251 -classpath C:\Users....kobalt\wrapper\dist\kobalt-0.780\kobalt\wrapper\kobalt-0.780.jar com.beust.kobalt.wrapper.Main --init idea __ __ __ __ __ / //_/ ____ /...

@RandyKahle Nice to hear that it works for you!

@cbeust But what the reason to keep this? Could you please add some use case to think about?

Yep, thanks! Now I see that this is some kind of flexibility which probably will be handy for some users.

@pabl0rg , @cbeust Tried --init kotlin and then --init idea and still have NPE: