kotlinlang #kobalt

11/17/2015, 7:18 PM

Filed an issue about that

11/17/2015, 7:18 PM

what wrapper?

11/17/2015, 7:18 PM

your kotlin project needs to depend manually on the jar produced by your first project

11/17/2015, 7:19 PM

I didnt even have it spit out a jar haha

11/17/2015, 7:19 PM

It will if you call

assemble

11/17/2015, 7:20 PM

I have a feeling we’re on the verge of a breakthrough

11/17/2015, 7:21 PM

11/17/2015, 7:21 PM

Still unresolved reference Protocol

11/17/2015, 7:21 PM

Do you know where that symbol is?

11/17/2015, 7:21 PM

util.kt just checked the file its totally fine no freak out (I can even run the project via intellij itself)

11/17/2015, 7:22 PM

So no kobalt bug so far

11/17/2015, 7:22 PM

11/17/2015, 7:23 PM

cl;ean seems to totally wipe kobaltBuild/libs

11/17/2015, 7:23 PM

simple smile

11/17/2015, 7:23 PM

Indeed it does

11/17/2015, 7:23 PM

I would not call that a bug

11/17/2015, 7:24 PM

But how am I meant to depend on a generated file that is instantly blown away by the second project building

11/17/2015, 7:24 PM

Yeah I warned you that would happen simple smile

11/17/2015, 7:24 PM

Define a different

buildDir

for your first project

11/17/2015, 7:25 PM

javaProject { buildDirectory = “javaBuild” }

or something

11/17/2015, 7:26 PM

This is getting kinda complicated as hell simple smile

11/17/2015, 7:26 PM

I know, you’re mixing languages and it’s not supported

11/17/2015, 7:26 PM

Totally understand if you want to give up until kobalt gets better at that

11/17/2015, 7:27 PM

Still unresolved simple smile

11/17/2015, 7:27 PM

your dependency in the kotlin dependencies should be something like

file(“javaBuild/libs/credit-…jar”)

11/17/2015, 7:28 PM

whatever the java jar name was

11/17/2015, 7:28 PM

compile(file("javaBuild/libs/credits-java-0.00.1a.jar"))

11/17/2015, 7:29 PM

11/17/2015, 7:29 PM

11/17/2015, 7:29 PM