Frederik Bertling

The core of realm is not written in kotlin. This project just contains the bindings.

When adding moko-resources folder to jsMain/iosMain etc. a new resource object is created. This does not happen for jsTest/iosTest etc.

Hey, thanks for addressing this issue! I tried beta-2 with createBuildInfoTask generating resources defined as the tasks output. ``` afterEvaluate { multiplatformResources.resourcesSourceSets["commonMain"].srcDir(createBuildInfoTask) } ``` The directory is read correctly and...

When using an explicit `dependsOn`, it often results in complex explicit task dependencies that have to follow (see the linked thread). I have no experience in Gradle plugin coding, but...

I'm getting this error most of the time too on kotlin 1.8.0 and 1.8.10 on a multi module project

My fix currently is to use the shared module resource path for the moko generated webpack config in the js application module instead of the applications module resource path `const...

I still have to add this webpack config to the web project ``` // noinspection JSUnnecessarySemicolon ;(function(config) { const path = require('path'); const MiniCssExtractPlugin = require('mini-css-extract-plugin'); const mokoResourcePath = path.resolve("/projectpath/shared/build/generated/moko/jsMain/appnameshared/res");...

It is similiar to the generated configs, but it adds the resource part of the **shared** module to the **web** module. Yes I have applied the multiplatform and moko plugin...

Hi, sorry I didn't specify the environment enough. When using app engine standard for java 11 there is no appengineRun task. I guess it is only for the old java...

Any news on this?