I had a codegen plugin that was generating kotlin and using project.sourceSets.main.kotlin.srcDirs

and that plugin was shared by other java projects that do not use kotlin

but use the plugin for other generation purposes

Is there a simpler way for specifying multiple annotations?

When i write:

@User uploaded a file: Untitled

It doesn't look very readable

@Paul Woitaschek you could always specify them separately one by one:

@field:Inject
@field:ObserveOn
lateinit var ...

Today at 3 PM CET (~2.5 hours from now I'll be streaming some Kotlin development at https://www.youtube.com/c/DmitryJemerov/live … . Please stop by and watch! I'll be rebuilding a prototype of a game (one could call it a roguelike) that I started building in C++ a few years back.

@yole will it be in english?

@mzgreen yes, it will be in English

@yole will it be recorded for later viewing?

sure

Dmitry Jemerov started streaming.

Doesn’t look like related to Kotlin in any way

Recording:

Would there be a way to have an artifact (jar) compiled from Kotlin src that doesn't have a dependency on stdlib? Right now I have a

Caused by: java.lang.ClassNotFoundException: Didn't find class "kotlin.jvm.internal.Intrinsics"

when using such artifact. If these kind of classes/functions added to the code during compilation were a separate dependency, which stdlib would also depend upon, I could depend on that instead.

@mg6maciej We had something like that (

kotlin-runtime

artifact which

kotlin-stdlib

depends on) in 1.0, but decided to merge them in Kotlin 1.1 https://blog.jetbrains.com/kotlin/2017/01/kotlin-1-1-whats-coming-in-the-standard-library/

I knew you would say that...

Oh well. I guess it's too much to ask for. Wouldn't be commonly required "feature".

You could try to merge the required classes from the runtime into your jar, if you do not want to take the entire stdlib as a dependency, but ensure that you have relocated them to another package.

But how would I such case code added during compilation use classes from different package?

It's not that I can change that without modifying compiler or something, can I?

Usually that is done at post-compilation phase

So you compile your code as usual, and then apply some tool (maven-shade-plugin or gradle shadow plugin) that post-processes the resulting classes and changes the references to them.

Oh, right. Probably too much of a hassle.

I won't use libs created in Kotlin from pura Java project anyway.

If it was the old (1.0) way, I could make it easy for someone else to do that tho.

The new way is no different than the old as far as your consumers are concerned

Their build system will pull the transitive dep and they don't care if it's a runtime jar or a stdlib jar