I have already done the following:
- forked https://github.com/JetBrains/kotlin
- cloned my fork and from there:
- git fetch upstream
- git merge upstream/master
- ant -f update_dependencies.xml (if needed)
- ant dist (same as ant -f build.xml or even just ant from what I could see)
- cd libraries && mvn [-PlocalKotlin] clean package
If so, are steps 3 to 5 run by the Kotlin Compiler and Plugin build configuration? If not, why?
One of the reasons I ask is because I noticed that the version of the IDEA snapshot in update_dependencies.xml had recently been upgraded from 116 to 118 whilst the IDEA CE build itself had not been successful for a while and therefore the last successful build remained stuck at version 116. Yet, none of the Kotlin builds picked up this problem. Step 3 failed on the command line as expected.
Secondly, after locally downgrading the version back to 116, I got several compilation failures for stdlib on the command line (step 5) due to methods not being implemented or (Jet) classes/methods not being found after repeated attempts over the past 24 hours (see the attached mvn_libraries.log). Again, none of the Kotlin builds picks up these problems.
This made me wonder whether I had correctly followed the instructions from this thread and from the Getting Started guide, and arguably more importantly, it made me wish for an ideally new build configuration that faithfully mirrors the steps that existing and aspiring committers should be executing on the command line before eventually pushing back to https://github.com/JetBrains/kotlin. This configuration would have picked up both of the above issues.
How does that sound, folks?
ant_dist.log.zip (1.69 KB)
mvn_libraries.log.zip (3.38 KB)
ant_update_dependencies.log.zip (636 Bytes)