however current version of kotlin 1.3. There is no...

# announcements

[ShootingStar]

however current version of kotlin 1.3. There is no expectedBy

[gildor]

It’s part of old MPP plugin, new MPP don’t have this

[gildor]

Why do you want to split?

[ShootingStar]

The same reason we split as a module

[gildor]

I mean you can have multiple modules

[ShootingStar]

so 🙂 how?

[gildor]

I probably misunderstood you, I thought tthat you talking about spliting module to multiple platfroms

[gildor]

so just create multiple modules and use usual Gradle dependencies API:

[gildor]

dependencies {
implementatation(project(“:some-other-module”))
}

[ShootingStar]

unfortunately it doesn’t work

[gildor]

Maybe you could than show some error message

[ShootingStar]

I will wait a sec mate 🙂

[ShootingStar]

Could not determine the dependencies of task ':app0:compileKotlinJvm'.
> Could not resolve all task dependencies for configuration ':app0:jvmCompileClasspath'.
   > Could not resolve project :ein.
     Required by:
         project :app0
      > Unable to find a matching variant of project :ein:
          - Variant 'metadataApiElements':
              - Required org.gradle.usage 'java-api' and found incompatible value 'kotlin-api'.
              - Found org.jetbrains.kotlin.localToProject 'public' but wasn't required.
              - Required org.jetbrains.kotlin.platform.type 'jvm' and found incompatible value 'common'.
          - Variant 'metadataCompile':
              - Required org.gradle.usage 'java-api' but no value provided.
              - Found org.jetbrains.kotlin.localToProject 'local to :ein' but wasn't required.
              - Required org.jetbrains.kotlin.platform.type 'jvm' and found incompatible value 'common'.
          - Variant 'metadataCompileOnly':
              - Required org.gradle.usage 'java-api' but no value provided.
              - Found org.jetbrains.kotlin.localToProject 'local to :ein' but wasn't required.
              - Required org.jetbrains.kotlin.platform.type 'jvm' and found incompatible value 'common'.
          - Variant 'metadataDefault':
              - Required org.gradle.usage 'java-api' but no value provided.
              - Found org.jetbrains.kotlin.localToProject 'local to :ein' but wasn't required.
              - Required org.jetbrains.kotlin.platform.type 'jvm' and found incompatible value 'common'.

[ShootingStar]

I add depedency like this

sourceSets {
        commonMain {
            dependencies {
                api project(':ein')
                implementation kotlin('stdlib-common')
            }
        }
 ...

[ShootingStar]

of course i tried implementation too

[ShootingStar]

it gave me the same error

[Big Chungus]

In new mpp modules are replaced by source sets. Create a new source set from preset and make other source sets depend on it

[gildor]

It justt works for me with Gradle 5.6.1 and Kotlin 1.3.50

[gildor]

In new mpp modules are replaced by source sets

It’s incorrect

[ShootingStar]

Did you define jvmMain?

[gildor]

module != sourceSet

[ShootingStar]

before entrypoint define, It works well however, after define entrypoint (jvmMain) it complain like as the above error

[gildor]

Modules are much more better abstraction, which provide actual encapuslation, source set is just additionl dir

[Big Chungus]

@gildor You are correct, I meant on the high level they can be treated as interchangeable. Although each has differences.

[gildor]

Oh which level?

[gildor]

For example Gradle compiles different modules in parallerl, but you cannot do this for different source sets of the same platform

[gildor]

you can have dependency on module, you cannot depend on single source set, so they are not interchangable at all

[Big Chungus]

On the level where you're only worried about the dependency/code management.

[Big Chungus]

So having the code in separate sourceSet or module and having another sourceSet or module depend on it achieves the same

[gildor]

exactly, in terms of dependency/code management it’s completely different story

[gildor]

you cannot have dependency from one source set of one module to another source set of another module

[gildor]

save for modules. Source set is just an additional root dir with sources of the same moduke

[gildor]

@ShootingStar Yes, it still works for me with JVM target

[ShootingStar]

hmm…what did I wrong then

[ShootingStar]

could you provide a repo?

[gildor]

https://github.com/gildor/knel/commit/b3a8286e5eafa6cc48d9db1be0a68c31b6f45bf6

[gildor]

probably you have this error because you add this module as dependency to JVM target, instead of common

[ShootingStar]

I can’t say thank you enough 🙂

[ShootingStar]

I will have a look

[ShootingStar]

@gildor Definitely yours working but I have few questions.

[ShootingStar]

- what is difference depedencies between in and out of sourceSets?

[gildor]

in and out of sourceSets?

[ShootingStar]

the depedencies in your project it is not in the

kotlin {
  ... 
  sourceSets{
...

[gildor]

should be no difference

[gildor]

I prefer Gradle convention for dependencies declaration than custom DSL of Kotlin MPP plugin

[gildor]

but those configurations are provided by Kotlin MPP plugin, nothing custom, so it should work in the same way

[ShootingStar]

The only difference your code and mine is mine is inside ’kotlin->sorucesets->commonmain->depedencies

[ShootingStar]

but anyway 🙂 your code is definitely working one so I will follow your style

[gildor]

Changed to sourceSet syntax still works for me

[ShootingStar]

arrrrggghhh 😞 then why mine

[gildor]

Which version of Gradle/Mpp plugin do you use?

[ShootingStar]

1.3.50 // 5.2.1

[gildor]

5.2.1 is a way too old Gradle

[gildor]

5.2.1 doesn’t support Gradle Metadata 1.0, so it also may be a problem

[ShootingStar]

😭 okay I will update it

[ShootingStar]

yes it works now. targets + gradle update works @gildor thank you heaps

[gildor]

👍

[gildor]

yeah, most probably it’s a problem with targets, they should match to be used in another module common source set