Cedric Beust

Ok but how do I determine which dependencies get exported?

Mmmh... Currently, all dependencies are automatically exported, i.e. if you have project A with dependency `dep1`, then any project that depends on A will automatically get `dep1` on its classpath....

@dmitry-zhuravlev Any thoughts?

@dmitry-zhuravlev I don't think we need to deprecate `--init idea`, I should just update it to the correct format.

@dmitry-zhuravlev @CaelumF is on the #kobalt Slack channel, feel free to jump in if you want to talk to him directly.

Sorry forgot about this. Yes, I'm open to that, I should be able to take a look in the next few days.

Now in Kobalt 0.880. You still receive `DependencyData` but that class has an additional `children` constructor parameter: ``` class DependencyData(val id: String, val scope: String, val path: String, val children:...

Yes, I only return the `compile` dependencies for now. It's trivial to fix: https://github.com/cbeust/kobalt/blob/master/src/main/kotlin/com/beust/kobalt/app/remote/DependencyData.kt#L68-L71

But what the server sends you is not `IClasspathDependency`, it's `DependencyData`, which includes the scope: ``` class DependencyData(val id: String, val scope: String, val path: String, val children: List =...

@dmitry-zhuravlev Probably just a change in `plugin.xml`?