nice

Lesson learned: for generic directory names like

”build”

, prefix with a dot:

”./build”

@kittinunf has left the channel

@cedric? are you around? made another project, did —init, it made a Build.kt file, added dependencies, all were fetched except for Spek, it reports

Cannot resolve org.jetbrains.spek:spek:. ignoring

and yet that is working in my other project. Also checkVersions is still ignoring spek. Not sure it’s Kobalt’s fault though: the repo at jetbrains/all has only old Spek builds.

-.txt

@codeslubber: "Spek has not been released yet and as such is not made available on Maven Central. However you can download it from the JetBrains Artifactory."

You need to add JetBrains' server as a repo

did that

the project (not this new one), that you fixed the other day by recommending going up to 186, you did yourself by just upping the version number, with the same settings.. ??

Try this:

./kobaltw --resolve org.spek:spek:0.1-SNAPSHOT

OMG

ok, it lost it’s mind, it’s looking for it in the android-sdk dir???

***** ERROR java.io.FileNotFoundException: /usr/local/android-sdk/extras/android/m2repository/org/spek/spek/0.1-SNAPSHOT/spek-0.1-0.1

No that's a bug I introduced in the latest IDEA plug-in 😞

whoops

oh wait

no it's not

That one is weird indeed, not sure why it ended up there

I did get the latest plugin and may have done sync first

is that in a config file? wait

don’t tell me

let me do a find

It's not related to the IDEA plug-in, forget I said that

ok

maybe somehow it is there

For me it ended up in

C:\Users\cbeust\.kobalt\repository\org/spek/spek/0.1-SNAPSHOT/spek-0.1-0.1-SNAPSHOT.jar

right

that’s where I showed the files were put when built in the last project

btw, I tried to use resolve before but did not know what it wanted for the id