This follows our naming convention and fixes a problem with production sources in *.tests module, which causes inconveniences during generation runtime module descriptors (IJPL-109).
GitOrigin-RevId: 35638e51a34f009bf327ecf8802cf5186ac220ce
This change introduces RuntimeModuleRepository API which will be used to determine paths to classes and other resources of modules at runtime. It also adds RuntimeModuleRepositoryBuilder which generates descriptors for modules during compilation of intellij project (this is controlled by a registry key which is switched off by default for now).
GitOrigin-RevId: be33235ec0cdb7ea55a925e753b9b58a3ca63ac3
Split performance plugin into core (and move it to community), async and YK. Move Cache Value Profiler to separate plugin.
GitOrigin-RevId: 80e68080197e86d40c76be45d5438ec0eee39818
This is needed to get rid of dependencies on PSI in workspaceModel.codegen module and extract it to a separate library (IDEA-297350).
GitOrigin-RevId: 36cd0cafc04b6f7f92a4c746fbec473b35b5f925
This is needed because production parts of these modules have language level 11, whereas tests depend on testFramework modules with language level 17, and this causes compilation errors if Kotlin code calls inline functions from module with a higher Java version.
GitOrigin-RevId: a7f88de0171cb3074d52b60e05bb280a08fd51e5
Project model for light project must not be changed in the test code because it's shared between tests, a new LightProjectDescriptor should be configured instead. Changes in global settings must be restored when test finishes to avoid problems in other tests. In order to execute test on TeamCity, its module must be added to dependencies of one of *.main modules.
GitOrigin-RevId: c9d5f03d2a26402359785f0d3059e9184753bf9c
If you are using 213 IDEA you need the 1.6.10 IDE plugin.
Use scope `PROVIDED` to trigger downloading but not add library to the runtime
Co-authored-by: Nikita Bobko <nikita.bobko@jetbrains.com>
GitOrigin-RevId: f8c9d9d91086f224c2835ca19a1ef7bf3fcd124d
This is needed to ensure that tests from them will be executed in Community Tests configuration, if they aren't assigned to some test group explicitly. If they are assigned, adding to community.main classpath shouldn't hurt.
GitOrigin-RevId: af9904fded920f39cf98b320c9a2868b6729feef
These tests should not be run in Community Tests configuration since the main part of the plugin is in ultimate part of the repository, but they should be executed along with other frameworks tests.
GitOrigin-RevId: 0a70ccc4983e9781b59a65b103af53c52b867f33
This is needed to run them on TeamCity, because the default Ultimate Tests configuration skip tests from community part.
GitOrigin-RevId: 8cd79abbbb39d62089fcb685e1d60fccce0322ac
This way we'll be able to reuse code from testFramework in them. (We cannot add dependency on testFramework to platform.execution.impl module because it'll lead to circular dependencies.)
GitOrigin-RevId: 678bf68acb047aeecd949da57c760977211d0f71
