so there’s something odd going on in the lifecycle. and logging vanishes off in the ether somewhere.

I stick with my gut feeling that the executor is being shut down prematurely

I suspect slipping a sleep() in Main.kt for a few seconds would confirm that

Are you able to run Kobalt from IDEA yet?

yes

at least, in the kobalt project itself

Then put a sleep() in there

in

DynamicGraphExecutor

?

No,

Main.kt:56

@cedric: still pushing to bitbucket?

No

All github

well, I think, unless I made a mistake, I’m seeing some pull anomalies

Going to remove all the contributors on bitbucket to avoid incidents

the rejection still stings. 😄

Your bits are welcome on github simple smile

@cedric: the —init command doesn’t seem to work?

it just prints the usage for me

CHeck out kobaltw, at some point I checked in one without $*

actually might even still be there

i’m using the latest release

but yeah that was the issue

Fixing that

does kobalt auto update itself?

Very close: you’ll receive a notification at the end of your build if a new version is available

I’m pushing .149 right now, hold on

hm, it says it can’t resolve my dependency from maven

Caused by: com.beust.kobalt.maven.KobaltException: Couldn't resolve nl.komponents.kovenantkovenant2.7.0 at com.beust.kobalt.maven.MavenDependency.<init>(MavenDependency.kt:40) at com.beust.kobalt.maven.DepFactory.create(DepFactory.kt:45) at com.beust.kobalt.maven.DepFactory.create$default(DepFactory.kt:23)

There 0.149 available, you should see a message if you launch

./kobaltw