Dmitry Savvinov
2c0ef592e6
- Introduce DSL for declaration of contracts. Functions and classes in this DSL do not bear any computational semantics: in fact, they all do not exist on runtime. Whole work of extracting semantics from such calls is done by special parts of compiler - To make distinguishing those declarations more robust and convenient, introduce internal annotation @ContractsDSL - Turn off InlineChecker inside contracts DSL. We do this, because some functions from DSL should take any possible lambda, so we can't write any type besides 'Function<R>'. However, InlineChecker will complain if we will pass inlined lambda in such function -- though, this is false positive because we know that functions from contracts DSL will never be executed - Change testData on HierarchyTestWithLib, where new enum from kotlin.internal changed expected output ========== Effect System introduction: 7/18
Kotlin Libraries
This area of the project is all written in Kotlin and assumes you've got the Kotlin IDEA plugin installed.
This area of the project uses Gradle and Maven for its build. When you open this project directory in IDEA the first time, it suggests you to import both gradle and maven projects. After importing you'll be able to explore and run gradle tasks and maven goals directly from IDEA with the instruments on the right sidebar.
Building
You need to install a recent Maven distribution and setup environment variables as following:
JAVA_HOME="path to JDK 1.8"
JDK_16="path to JDK 1.6"
JDK_17="path to JDK 1.7"
JDK_18="path to JDK 1.8"
The main part of the Kotlin standard library, kotlin-stdlib, is compiled against JDK 1.6 and also there are two extensions
for the standard library, kotlin-stdlib-jre7 and kotlin-stdlib-jre8, which are compiled against JDK 1.7 and 1.8 respectively,
so you need to have all these JDKs installed.
Be sure to build Kotlin compiler distribution before launching Gradle and Maven: see root ReadMe.md, section "Building".
Core libraries are built with gradle, you can run that build using the gradle wrapper script even without local gradle installation:
./gradlew build install
Note: on Windows type
gradlewwithout the leading./
This command executes the build task, which assembles the artifacts and run the tests, and the install task, which puts the artifacts to the local maven repository to be used by the subsequent maven build.
The rest of tools and libraries are built with maven:
mvn install
If your maven build is failing with Out-Of-Memory errors, set JVM options for maven in MAVEN_OPTS environment variable like this:
MAVEN_OPTS="-Xmx2G"
Gradle Plugin
Gradle plugin sources can be found at the kotlin-gradle-plugin module.
To build the Gradle plugin and the subplugins, first build the core libraries and other tools (the Gradle and Maven builds above) and then, inside tools/gradle-tools, run:
gradlew clean install
Gradle integration tests
Gradle integration tests can be found at the kotlin-gradle-plugin-integration-tests module.
To run integration tests, run from tools/gradle-tools:
gradlew :kotlin-gradle-plugin-integration-tests:test
The tests that use the Gradle plugins DSL (PluginsDslIT) also require the Gradle plugin marker artifacts to be installed from tools/gradle-tools:
gradlew -Pmarker_version_suffix=-test :kotlin-gradle-plugin:plugin-marker:install :kotlin-noarg:plugin-marker:install :kotlin-allopen:plugin-marker:install