* </p>
 * <p>
 * With changes during 3.2.2 release MavenProject is closer to being immutable after construction with the removal of
 * all components from this class, and the upfront construction taken care of entirely by the {@link ProjectBuilder}.
 * There is still the issue of having to run the lifecycle in order to find all the compile source roots and resource

  }

  @Test
  @TestMetadata("javaPropertyGetter.kt")
  public void testJavaPropertyGetter() {
    runTest("analysis/analysis-api/testData/components/callResolver/resolveCall/javaPropertyGetter.kt");
  }

  @Test
  @TestMetadata("javaPropertyGetter_unqualified.kt")
  public void testJavaPropertyGetter_unqualified() {

    KtTestUtil.assertAllTestsPresentByMetadataWithExcluded(this.getClass(), new File("analysis/analysis-api/testData/components/expressionInfoProvider/isUsedAsExpression"), Pattern.compile("^(.+)\\.kt$"), null, true);
  }

  @Test
  @TestMetadata("annotatedExpr.kt")
  public void testAnnotatedExpr() {
    runTest("analysis/analysis-api/testData/components/expressionInfoProvider/isUsedAsExpression/annotatedExpr.kt");
  }

  @Test

 * can be changed (See <a href="../../../resolver.html">Setting Name
 * Resolution Properties</a>). The servername and path components are
 * not case sensitive but the domain, username, and password components
 * are. It is also likely that properties must be specified for jcifs
 * to function (See <a href="../../overview-summary.html#scp">Setting