<option name="scriptParameters" value="" />
      <option name="taskDescriptions">
        <list />
      </option>
      <option name="taskNames">
        <list>
          <option value="analysisLowLevelApiFirAllTests" />
          <option value="--tests" />
          <option value="*" />
        </list>
      </option>
      <option name="vmOptions" />
    </ExternalSystemSettings>

      <option name="scriptParameters" value="" />
      <option name="taskDescriptions">
        <list />
      </option>
      <option name="taskNames">
        <list>
          <option value=":analysis:symbol-light-classes:test" />
          <option value="--tests" />
          <option value="*" />
        </list>
      </option>
      <option name="vmOptions" />
    </ExternalSystemSettings>

      <inspection_tool class="SubjectLimit" enabled="true" level="WARNING" enabled_by_default="true" />
    </profile>
  </component>
  <component name="IssueNavigationConfiguration">
    <option name="links">
      <list>
        <IssueNavigationLink>
          <option name="issueRegexp" value="[A-Z]+\-\d+" />
          <option name="linkRegexp" value="http://youtrack.jetbrains.com/issue/$0" />
        </IssueNavigationLink>

            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>
        <field>
          <name>description</name>
          <version>1.0.0+</version>

      <option name="scriptParameters" value="" />
      <option name="taskDescriptions">
        <list />
      </option>
      <option name="taskNames">
        <list>
          <option value=":analysis:low-level-api-fir:tests-jdk11:test" />
          <option value="--tests" />
          <option value="*" />
        </list>
      </option>
      <option name="vmOptions" />
    </ExternalSystemSettings>

              <!-- was only a workaround for Plexus Container, hopefully never used by anyone else -->
              <exclude>org.apache.maven.plugin.DefaultBuildPluginManager#setMojoExecutionListeners(java.util.List)</exclude>

      <option name="scriptParameters" value="" />
      <option name="taskDescriptions">
        <list />
      </option>
      <option name="taskNames">
        <list>
          <option value=":analysis:decompiled:decompiler-to-file-stubs:test" />
          <option value="--tests" />
          <option value="*" />
        </list>
      </option>
      <option name="vmOptions" />
    </ExternalSystemSettings>

            and {@code test-jar}: see <a href="../maven-core/artifact-handlers.html">default
            artifact handlers</a> for a list. New types can be defined by extensions, so this is not a complete list.
            ]]>
          </description>
          <type>String</type>
          <defaultValue>jar</defaultValue>
        </field>
        <field>

            lines could make c.g.c.base.testModule transitively inherit from extra modules. If some
            of those modules are ones that it uses but forgets to list in its own <inherits>, we'd
            like to get an error. Currently we do, but if we add the extra <inherits> lines, we
            won't.

      <option name="externalSystemIdString" value="GRADLE" />
      <option name="scriptParameters" value="" />
      <option name="taskDescriptions">
        <list />
      </option>
      <option name="taskNames">
        <list>
          <option value="generateFrontendApiTests" />
        </list>
      </option>
      <option name="vmOptions" />
    </ExternalSystemSettings>