got it

i'll try this morning

thank you

It's still running with jvmTarget 1.6 though (the default), because of the issue we identified yesterday.

k, so kotlin 1.1, java 1.6

I also had some issues with FXLauncher after the update. The old std-lib was still loaded, so I had to remove my local app cache so it would redownload the new stdlib. Checking what that's about.

@jchildress Correct!

@ron The @DslMarker might be a good fit for TornadoFX 2.0. We need to investigate how much impact this would have on existing code, and if the benefits outweigh the API change.

I suspect they might.

We'd have a lot less "subtle bugs".

@edvin mvn clean test works fine...

tested with a small sample application I have and it works too

thanks

Perfect 🙂

hmmz my intellij does not offer 1.1 as kotlin settings

updating the plugin

@edvin did you put the api verson to 1.1 too?

@ron You need to update the plugin first. Yes, I used 1.1 across the board.

coroutines enabled with warnings?

@ron That shouldn't matter, I left it as it was.

and in maven "kotlin-stdlib-jre8" ?

Yes 🙂

I guess that doesn't do much of a difference when we haven't enabled jvm-target 1.8 though. Hopefully that bug will be sorted quickly.

keepassFX starts again 🙂

Sweet!

I'm glad we make software for developers or this would have been very painful 🙂

ROFL, I think we need a new flag for fxlauncher "--cleanLocalCache"

@ron Haha 🙂 That would actually be good. But I'm not sure why it wasn't updated. Need to investigate later.

In the weekend I will add the flags

--simpleError

,

--stopOnUpdateError

and

--cleanLocalCache

What will

simpleError

do?