</entry>
      </map>
    </option>
    <option name="testDataFiles">
      <array>
        <option value="$PROJECT_DIR$/compiler/testData" />
        <option value="$PROJECT_DIR$/compiler/fir/analysis-tests/testData" />
        <option value="$PROJECT_DIR$/compiler/tests-spec/testData" />
        <option value="$PROJECT_DIR$/js/js.translator/testData" />
        <option value="$PROJECT_DIR$/compiler/fir/raw-fir/psi2fir/testData" />

<?xml version="1.0" encoding="UTF-8"?>
<project version="4">
  <component name="KotlinCompilerSettings">
    <option name="additionalArguments" value="-version -Xallow-kotlin-package -Xskip-metadata-version-check" />
  </component>
  <component name="KotlinJpsPluginSettings">
    <option name="version" value="2.0.20-dev-2651" />
  </component>

            this case, you want the user to modify {@code <build><finalName/></build>} rather
            than specifying a value for finalName directly in the plugin configuration section. It is also useful to
            ensure that - for example - a List-typed parameter which expects items of type Artifact doesn't get a List
            full of Strings.
          </description>
        </field>

          <option value="io.reactivex.annotations.Experimental" />
          <option value="org.apache.http.annotation.Beta" />
          <option value="org.gradle.api.Incubating" />
          <option value="org.jetbrains.annotations.ApiStatus.Experimental" />
          <option value="rx.annotations.Beta" />
          <option value="rx.annotations.Experimental" />
        </set>
      </option>
    </inspection_tool>

            dependencies in this section are not immediately resolved. Instead, when a POM derived
            from this one declares a dependency described by a matching groupId and artifactId, the
            version and other values from this section are used for that dependency if they were not
            already specified.</description>
          <association>