(problemsCount == 1) ? "problem was" : "problems were",
                        result.getProjectId());

                if (request.isShowErrors()) { // this means -e or -X (as -X enables -e as well)
                    for (ModelProblem problem : result.getProblems()) {
                        String loc = ModelProblemUtils.formatLocation(problem, result.getProjectId());

            problemCollector.problems().map(BuildSession::convert).forEach(problems::add);
            if (problemCollector.problemsOverflow()) {
                problems.add(
                        0,
                        new DefaultModelProblem(
                                "Too many model problems reported (listed problems are just a subset of reported problems)",

     */
    @Nonnull
    List<Profile> getActiveExternalProfiles();

    /**
     * Gets the problem collector that collected problems encountered during the project building.
     *
     * @return the problem collector that collected problems encountered during the project building
     */
    @Nonnull
    ProblemCollector<ModelProblem> getProblemCollector();

    /**

    "functionalTests": true,
    "crossVersionTests": true
  },
  {
    "name": "problems",
    "path": "platforms/ide/problems",
    "unitTests": true,
    "functionalTests": true,
    "crossVersionTests": false
  },
  {
    "name": "problems-api",
    "path": "platforms/ide/problems-api",
    "unitTests": true,
    "functionalTests": true,
    "crossVersionTests": false
  },

    val docsTestTriggers: List<OsAwareBaseGradleBuildType>

    val flakyTestQuarantineTriggers: List<OsAwareBaseGradleBuildType>

    init {
        features {
            buildReportTab("Problems Report", "problems-report.html")
            if (stage.specificBuilds.contains(SpecificBuild.SanityCheck)) {
                buildReportTab(
                    "API Compatibility Report",

For a **web API**, it normally involves putting it in a **remote machine**, with a **server program** that provides good performance, stability, etc, so that your **users** can **access** the application efficiently and without interruptions or problems.

This is in contrast to the **development** stages, where you are constantly changing the code, breaking it and fixing it, stopping and restarting the development server, etc.

            <option value="$PROJECT_DIR$/platforms/ide/ide-plugins" />
            <option value="$PROJECT_DIR$/platforms/ide/problems" />
            <option value="$PROJECT_DIR$/platforms/ide/problems-api" />
            <option value="$PROJECT_DIR$/platforms/ide/problems-rendering" />
            <option value="$PROJECT_DIR$/platforms/ide/tooling-api" />

        testing/architecture-test/build/reports/binary-compatibility/report.html => binary-compatibility-reports
        build/reports/dependency-verification/** => dependency-verification-reports
        build/reports/problems/problems-report.html
        """.trimIndent()

    setArtifactRules(artifactRuleOverride ?: defaultArtifactRules)
    paramsForBuildToolBuild(buildJvm, os, arch)
    params {

        }

        // The fall-through indicates that the artifact cannot be found;
        // for instance if package produced nothing or classifier problems.
        return null;
    }

    private File determineBuildOutputDirectoryForArtifact(final MavenProject project, final Artifact artifact) {
        if (isTestArtifact(artifact)) {

   * Executor#execute execute}, as in {@link CallerRunsPolicy}.
   *
   * <p>This executor is appropriate for tasks that are lightweight and not deeply chained.
   * Inappropriate {@code directExecutor} usage can cause problems, and these problems can be
   * difficult to reproduce because they depend on timing. For example:
   *
   * <ul>
   *   <li>When a {@code ListenableFuture} listener is registered to run under {@code