Alexey Tsvetkov 4ccec5218f Remove dirty output files when expanding IC scope early ...

Previously IC could go to the next iteration without removing
outputs for the files compiled during the last iteration.
For example, it could happen, when a multifile part is changed
(we add sources for other parts and recompile everything together).

In case of MPP it could lead to compile error, because
the compiler would see the same actual declarations from dirty sources
and dirty outputs from previous iteration (which should have been removed).
That behaviour did not raise an error before dc8240c24e
because actual declarations from binaries (e.g. compile classpath) were ignored.

    #KT-35957 Fixed

2020-04-18 06:05:44 +03:00

..

allPlatforms

Minor: move non-JPS MPP IC tests under incremental/mpp dir

2020-04-18 06:05:44 +03:00

jvmOnly/multifilePartChanged

Remove dirty output files when expanding IC scope early

2020-04-18 06:05:44 +03:00