- 07 6月, 2018 20 次提交
-
-
由 Anton Bannykh 提交于
js.libraries doesn't exist anymore
-
由 Mikhail Zarechenskiy 提交于
-
由 Svyatoslav Kuzmich 提交于
-
由 Svyatoslav Kuzmich 提交于
Fix KT-24542: insert labes for affected loops, breaks and continues statements during LabeledBlockToDoWhileTransformation
-
由 Pavel V. Talanov 提交于
-
由 Pavel V. Talanov 提交于
To avoid confusing with platform extension and debugging for 3 hours
-
由 Pavel V. Talanov 提交于
When creating multifile facades respect that facade files can be both in common and jvm parts #KT-23942 Fixed
-
由 Pavel V. Talanov 提交于
-
由 Pavel V. Talanov 提交于
-
由 Pavel V. Talanov 提交于
#KT-24115 Fixed
-
由 Pavel V. Talanov 提交于
-
由 Pavel V. Talanov 提交于
Note: can't use Module.cached to calculate data that depends on input other than the module itself (isTests in this case)
-
由 Pavel V. Talanov 提交于
-
由 Pavel V. Talanov 提交于
-
由 Pavel V. Talanov 提交于
-
由 Pavel V. Talanov 提交于
Do not show bytecode window for non-jvm platform modules #KT-24159 Fixed
-
由 Pavel V. Talanov 提交于
findClass* are supposed to return a single visible class from given scope with given fqname After sorting FakeFileForLightClass would sometimes be first in the list leading to exceptions like KT-24704 #KT-24704 Fixed
-
由 Pavel V. Talanov 提交于
-
由 Pavel V. Talanov 提交于
-
由 Pavel V. Talanov 提交于
-
- 06 6月, 2018 20 次提交
-
-
由 Alexey Tsvetkov 提交于
E.g. avoid building release variants for Android (extremely slow due to proguard minification, optimization)
-
由 Alexey Tsvetkov 提交于
-
由 Alexey Tsvetkov 提交于
Currently the test makes more harm than use: * It is too slow: two executions (with different Gradle versions) take 5 minute on CI. * It is unreliable: the test fails on CI for months with insignificant violation of the memory growth limit. After this change: * the memory growth limit is increased; * the test run count is decreased; * changes the test to use separate project with minimal amount of classes (we're not interested in compiler's memory leaks; only Gradle plugin specific ones);
-
由 Alexey Tsvetkov 提交于
-
由 Ilya Gorbunov 提交于
Even if they now have overloads that will be selected when these parameters are omitted. This is to preserve compatibility with the libraries compiled against the older library. #KT-24782 Fixed
-
由 Nicolay Mitropolsky 提交于
-
由 Nicolay Mitropolsky 提交于
-
由 Nicolay Mitropolsky 提交于
-
由 Nicolay Mitropolsky 提交于
no sense to keep difference
-
由 Mikhael Bogdanov 提交于
-
由 Mikhael Bogdanov 提交于
-
由 Mikhael Bogdanov 提交于
-
由 Mikhael Bogdanov 提交于
-
由 Roman Artemev 提交于
-
由 Alexey Tsvetkov 提交于
-
由 Alexey Tsvetkov 提交于
We run all tests with multiple Gradle versions now, so parametrized test is not needed anymore. Test cases are moved to relevant test classes. testKaptProcessorPath is removed because kapt1 is not supported anymore.
-
由 Alexey Tsvetkov 提交于
-
由 Alexey Tsvetkov 提交于
We don't support Gradle <= 3.5 at the moment, it does not make sense to have the code for Gradle < 2.14
-
由 Alexey Tsvetkov 提交于
-
由 Alexey Tsvetkov 提交于
-