There are several meta-modules:
- 'kotlin.all-tests' and 'kotlin.fir.all-tests'. Used as a test classpath on CI.
- 'kotlin.plugin' and 'kotlin.plugin-fir'. Used mainly for XML plugin descriptor resolution.
- 'intellij.kotlin.plugin.community.main' and 'intellij.kotlin.plugin.community.fir.main'. Used for running IDEA from sources.
All relevant Kotlin IDE plugin modules should be present in each of these meta-modules. In addition, there is 'KotlinPluginBuilder', a Groovy script which assembles plugin artifact JARs.
It is easy to forget putting newly created modules in each of these locations, so here is the consistency test.
GitOrigin-RevId: 990dfb1c5447e22ab89fb4aeb2cd3d8e937aa110
Some facts:
1. Kotlin plugin bundles own version of kotlin-stdlib and reflect (see KotlinPluginBuilder.groovy).
We bundle own version of stdlib and reflect (but not use the one which comes with IDEA) because
otherwise we would have runtime errors in compiler frontend which we depend on
(kotlinc.kotlin-compiler)
2. Kotlin plugin exists in two release cycles. We have special `kt-xxx-[kotlin_compiler_version]`
branches (e.g. kt-212-1.5.30 branch) in the repository where we put Kotlin plugin fixes which
should be delivered in KT release cycle.
2.1 The fact that we publish Kotlin plugin artifacts to marketplace from special kt-branches
leads to the fact that stdlib may be different in Kotlin plugin and IntelliJ IDEA. By
separating `kotlin-stdlib-jdk8` and `kotlinc.kotlin-stdlib` we make it obvious that Kotlin
plugin has it's own stdlib
This commit fixes broken incremental compilation in kt-212-master
on TeamCity because now we have to bootstrap only kotlinc.kotlin-stdlib.
Previously, we had to bootstrap kotlin-stdlib-jdk8 which caused problems
with incremental compilation because whole monorepo depends on this artifact.
Also now during kotlinc updates in `intellij/master` we don't have to update kotlin-stdlib-jdk8
every time to keep kotlinc version the same among different imls/xmls in the monorepo
https://jetbrains.team/im/code/258iod1xjiFZ?message=BK9Aq0SIM1A&channel=152Z1w0RwrFp
(cherry picked from commit 23b2a70604c5c578983b0d76cb8634b9ed301a59)
GitOrigin-RevId: 773c01c405f2eb9db8d88ce3c58e4bdcee66c085
KotlinPluginInternalApi annotation was replaced by generic IntellijInternalApi, which can be used in other plugins as well. So it becomes possible to use Kotlin compiler settings from the project configuration in almost all modules from Kotlin plugin, making Kotlin facets in these modules unnecessary. Removal of Kotlin facets simplifies project configuration and makes it easier to change settings of Kotlin compiler.
GitOrigin-RevId: 17590fab5769e3b79f47adb2af41b1dbcebf6e0a
Kotlin 1.5 doesn't write tag for 'jvmTarget' option if its value is '1.8', and does write it if its value is '1.6', so this change is needed to avoid modified iml files if the project is opened with Kotlin plugin 1.5 (see KTIJ-19019).
GitOrigin-RevId: 8fc21bf185ac8c23675123b904f25af5defcc98e
This commit is part of series of project model refactoring commits, look at neighborhood commits.
Check out last commits in this sequence.
These commit are done for sake of unification and making it easier to write cooperative compilation
prototype.
GitOrigin-RevId: 4ec18be4192e6ea9fe93f14e3e9fac83cec68c91
This commit is part of series of project model refactoring commits, look at neighborhood commits.
Check out last commits in this sequence.
These commit are done for sake of unification and making it easier to write cooperative compilation
prototype.
GitOrigin-RevId: 341fbb8bc02ad28a7e2113b859fba87756af5c37
