because SchemeManager doesn't use PathManager (by intention and historical reasons)

IDEA-177683 Gradle import uses wrong source/javadoc artifact for dependencies with multiple artifacts

assert that long processes like find in files or find usages are running under the cancelable indicator

Otherwise paths in project configuration which use macros won't be properly loaded by the external build process. This may happen if the project uses libraries from Maven repository for example.

IDEA-175682 maven - use default source root for modules that are not named "pom.xml" but still the only module in their directory

avoid dbl reporting/dbl running when multiple scopes are configured

Now paths to JUnit4 JARs are taken from IDEA project configurations so we won't need to update all these places after changing JUnit version, and tests won't be broken when JUnit JARs are taken from Maven repository.

use this to prevent possible light annotation PSI modifications