Files
openide/python/python-features-trainer
Mikhail Filippovandintellij-monorepo-bot 93ee57325f MRI-4541 don't export JUnit libraries from intellij.platform.testFramework
Stop exporting the JUnit library modules (intellij.libraries.junit4 / junit5 /
junit5.params and the junit5 launcher/jupiter variants) from modules that
re-exported them, so that every module declares the JUnit framework it actually
uses:

* intellij.platform.testFramework and intellij.platform.testFramework.tests
* intellij.appcode.tests
* intellij.kmm.performance.tests, intellij.kmm.testFramework.driver
* intellij.ide.starter.allure.annotations
* intellij.ide.starter.extended.screenshotComparator

The JUnit dependencies stay in those modules (their own sources use them), now
without `exported`. Modules that relied on the transitive export get direct
dependencies: scope="TEST" for test code and scope="PROVIDED" for test-framework
modules whose production sources use JUnit (this keeps JUnit off the product
runtime classpath). New JUnit entries are placed at the end of the module
dependency list. BUILD.bazel files and the JUnit entries in
buildScripts/suppressions.json are regenerated accordingly.

GitOrigin-RevId: 115c4a7d37a7759190788c2a7aa6b039cc7b6903
2026-06-16 13:31:21 +00:00
..