Sergey Igushkin
c4283de9cb
The traditional Gradle/Java model assumes several configurations, which are now deprecated, which are both `canBeConsumed = true` and `canBeResolved = true`. * compile, testCompile, etc. * runtime, testRuntime, etc. * default These configurations need to somehow resolve correctly to an appropriate platform-specific artifact when they contain an MPP library or project dependency. However, simply marking them with the Kotlin platform type attribute would put these configurations under considerations during Gradle variant aware depdendency resolution of project dependencies, which in order would lead to ambiguity (e.g. `compile` vs `runtime` vs `testCompile` vs ... vs `apiElements`). To deprioritize these configurations during dependency resolution, we mark them with a special attribute with a unique value in each project. Given that the values are different in different projects, Gradle will not choose a configuration marked by this attribute. But we still need 'project(path: '...', configuration: '...')` dependencies to work, and so, instead of rejecting those different values of the attribute, we say that all values are compatible, but when an ambiguity arises, choose the configurations not marked by this attribute, so effectively eliminating them from resolution. Issue #KT-27111 Fixed
Kotlin Libraries
This part of the project contains the sources of the following libraries:
- kotlin-stdlib, the standard library for Kotlin/JVM, Kotlin/JS and its additional parts for JDK 7 and JDK 8
- kotlin-reflect, the library for full reflection support
- kotlin-test, the library for multiplatform unit testing
- kotlin-annotations-jvm, the annotations to improve types in the Java code to look better when being consumed in the Kotlin code.
These libraries are built as a part of the root Gradle project.
Kotlin Maven Tools
This area of the project is the root for Maven build.
You can work with the maven modules of this maven project in IDEA from the root IDEA project. After importing you'll be able to explore maven projects and run goals directly from IDEA with the instruments on the right sidebar.
Building
You need to install a recent (at least 3.3) Maven distribution.
Before building this Maven project you need to build and install the required artifacts built with Gradle to the local maven repository, by issuing the following command in the root project:
./gradlew install
Note: on Windows type
gradlewwithout the leading./
This command assembles and puts the artifacts to the local maven repository to be used by the subsequent maven build. See also root ReadMe.md, section "Building".
Then you can build maven artifacts 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"