Marco Pennekamp 1870189e47 [AA] Fix write access configuration in unit test application environments ...

- We cannot configure the application's write action accessibility on a
  per-test basis because (1) the application may be shared across
  concurrent tests and (2) the application is usually cached, so the
  configuration will be missed entirely.
- There is actually a much easier solution to allow write access
  selectively: We can enable it in `runWriteAction` blocks, and keep it
  in a thread local to support concurrent test runs. As Analysis API
  tests never call `runWriteAction`, there will be no "analyze cannot be
  called from a write action" error, and if `analyze` is somehow called
  from a write action, it will now be caught.

^KT-63560 fixed

2023-11-20 16:29:26 +00:00

..

tests/org/jetbrains/kotlin/analysis/test/framework

[AA] Fix write access configuration in unit test application environments

2023-11-20 16:29:26 +00:00

build.gradle.kts

[Build] Fix the typo junit jupyter -> jupiter

2023-09-06 22:47:34 +00:00