<component name="ProjectRunConfigurationManager">
  <configuration default="false" name="Symbol Light Classes Tests" type="GradleRunConfiguration" factoryName="Gradle" folderName="Analysis">
    <ExternalSystemSettings>
      <option name="executionName" />
      <option name="externalProjectPath" value="$PROJECT_DIR$" />
      <option name="externalSystemIdString" value="GRADLE" />
      <option name="scriptParameters" value="" />
      <option name="taskDescriptions">

  </description>
  <defaults>
    <default>
      <key>package</key>
      <value>org.apache.maven.plugin.resources.remote</value>
    </default>
  </defaults>
  <classes>
    <class rootElement="true" xml.tagName="remoteResourcesBundle">
      <name>RemoteResourcesBundle</name>
      <version>1.1.0</version>
      <description>Root element of the remote-resources.xml file.</description>

  <defaults>
    <default>
      <key>package</key>
      <value>org.apache.maven.plugin.resources.remote</value>
    </default>
  </defaults>
  <classes>
    <class rootElement="true" xml.tagName="supplementalDataModels" xsd.compositor="sequence">
      <name>SupplementalDataModel</name>
      <version>1.0.0</version>

  <defaults>
    <default>
      <key>package</key>
      <value>org.apache.maven.usability.plugin</value>
    </default>
  </defaults>
  <classes>
    <class rootElement="true" xml.tagName="paramdoc">
      <version>1.0.0</version>
      <name>ExpressionDocumentation</name>
      <description>The root of a parameter plugin expression document.</description>
      <fields>

    tests, either. This causes it to fail to find AtomicLongMapTest.

    Our workaround is to tell GWT that util.concurrent and all other packages
    have prod supersource, even if they have none. GWT is happy to ignore us
    when we specify a nonexistent path.

    (I hope that this workaround does not cause its own problems in the future.)
-->
<super-source path="super"/>

    <artifactId>maven</artifactId>
    <version>4.0.0-beta-1-SNAPSHOT</version>
  </parent>

  <artifactId>maven-compat</artifactId>

  <name>Maven Compat (deprecated)</name>
  <description>Deprecated Maven2 classes maintained as compatibility layer.</description>

  <dependencies>
    <dependency>
      <groupId>org.apache.maven</groupId>
      <artifactId>maven-model</artifactId>
    </dependency>
    <dependency>

        <module name="UnusedImports"/>
        <module name="IllegalImport">
            <!--
                We shouldn't use jdk.internal types.
                
                com.beust and org.testng.collections has classes that look like Guava.

                We prefer to import javax.annotation and fully-qualify references to org.jetbrains.annotations.
            -->

        <option value="$PROJECT_DIR$/plugins/power-assert/testData" />
        <option value="$PROJECT_DIR$/analysis/analysis-api/testData" />
        <option value="$PROJECT_DIR$/analysis/symbol-light-classes/testData" />
        <option value="$PROJECT_DIR$/analysis/low-level-api-fir/testData" />
        <option value="$PROJECT_DIR$/native/native.tests/testData" />
      </array>
    </option>
  </component>

    <scriptSourceDirectory>${pom.basedir}/src/main/scripts</scriptSourceDirectory>

    <outputDirectory>${pom.build.directory}/classes</outputDirectory>
    <testOutputDirectory>${pom.build.directory}/test-classes</testOutputDirectory>
  </build>

  </properties>

  <build>
    <directory>${project.basedir}/target</directory>
    <outputDirectory>${project.build.directory}/classes</outputDirectory>
    <finalName>${project.artifactId}-${project.version}</finalName>
    <testOutputDirectory>${project.build.directory}/test-classes</testOutputDirectory>
    <sourceDirectory>${project.basedir}/src/main/java</sourceDirectory>