'classpath' makes sense only in case of Kotlin/Jvm, but not for
Kotlin/Js or Kotlin/Native. 'libraries' is common ground for a name.
For 'KotlinCompile' task 'getClasspath' and 'setClasspath' methods
are left with deprecation note.
^KT-32805 Fixed
This and new KotlinCompile task inputs dedicated for scripting
allowed providing proper Kotlin scripts compilation support without
eager configuration dependencies resolve.
^KT-32805 In Progress
This allows to drop SourceRoots intermediate container and replace it
with normal Gradle inputs. This inputs will use ant-style
patterns for filtering allowing Gradle to apply better caching
between builds.
KaptTask replaces ConventionTask parent with DefaultTask.
^KT-32805 In Progress.
'AbstractCompile' task has inputs that are related only to Java
compilation and should not used for Kotlin compile tasks.
'SourceTask' most probably will be deprecated in future Gradle releases
- https://github.com/gradle/gradle/issues/9040. Plus it has
old 'sources' with 'FileTree' type which is not stable
for task inputs snapshotting.
Another breaking change - 'destinationDir' task property is not longer
available. It is replaced by 'destinationDirectory' which uses Gradle
Provider API type.
^KT-32805 In Progress
With this annotation we can configure specific tests for
running on different platforms on TC and locally.
`supportedOn` shows the platform where the test should pass.
`enabledOnCI` configures on which platform test should be run on CI.
Previously commonCompilationDataPerFragment and
nativeCompilationDataPerFragment were declared as using
`mutableMapOf`, which will not offer the necessary 'compute' function
in IDE analysis.
KT-51386
The `kotlinExtension` check in consumerApiUsage function can be removed
when legacy MPP plugin `kotlin-platform-common` is also removed from
the code base.
Consumer configurations with following set of attributes:
* org.gradle.usage = 'kotlin-api'
* org.jetbrains.kotlin.platform.type = 'common'
are supposed to consume legacy `*.kotlin_metadata` artifacts.
And can be consumed by HMPP project with
"Compatibility Metadata Variant Enabled" flag. For such purpose
`metadataCompileClasspath` configuration is configured with attributes
mentioned above.
There is no sense to consume such artifacts in HMPP projects without
compatibility metadata variant. And in order to prevent
breaking changes in KGP ecosystem, legacy configurations are
reconfigured to consume new KLIB metadata artifacts. Instead of failing
on resolution.
^KT-50925 Verification Pending
[Gradle, JS] Use empty adapter to just dry run
[Gradle, JS] Not dry run, but full run
[Gradle, JS] Fix test to be failed without dry run
[Gradle, JS] Not use client twice
[Gradle, JS] Add test on mocha failing
[Gradle, JS] Fail mocha in case of infrastructure problems
Merge-request: KT-MR-5802
Merged-by: Ilya Goncharov <Ilya.Goncharov@jetbrains.com>
^KT-51623 fixed
Viacheslav Kormushkin