assertEquals(pom0Basedir, project1.getParent().getBasedir());
        assertNull(
                project1.getArtifact().getScope(),
                "dependencyManagement has overwritten the scope of the currently building child project");
    }

                public void execute(Task task) {
                    if (expectedOutputFile.exists() == false) {
                        throw new InvalidUserDataException(
                                "Building " + bwcVersion.get() + " didn't generate expected artifact " + expectedOutputFile
                        );
                    }
                }
            });
        });

Maven Settings Model

 This is the model for Maven settings in <<<org.apache.maven.settings>>> package,
 delegating content to {{{../../api/maven-api-settings/index.html}Maven 4 API immutable settings}}. All the effective model
 building logic from multiple settings files is done in {{{../maven-settings-builder/}Maven Settings Builder}}.

 The following are generated from this model:

import org.apache.maven.settings.SettingsUtils;
import org.apache.maven.settings.building.DefaultSettingsBuildingRequest;
import org.apache.maven.settings.building.SettingsBuilder;
import org.apache.maven.settings.building.SettingsBuildingRequest;
import org.apache.maven.settings.building.SettingsBuildingResult;
import org.apache.maven.settings.building.SettingsProblem;
import org.apache.maven.settings.crypto.SettingsDecrypter;

        if (Constants.DEFAULT_FIELD.equals(field) && defaultField != null) {
            return defaultField;
        }
        return field;
    }

    /**
     * Functional interface for building query builders with field and boost parameters.
     */
    protected interface DefaultQueryBuilderFunction {
        /**
         * Applies the function to create a query builder for the specified field and boost.

[dev-ml-list]: https://www.mail-archive.com/******@****.***/
[code-style]: http://maven.apache.org/developers/conventions/code.html
[core-it]: https://maven.apache.org/core-its/core-it-suite/
[building-maven]: https://maven.apache.org/guides/development/guide-building-maven.html

 */
package org.apache.maven.model.building;

import java.io.File;
import java.util.Date;
import java.util.List;
import java.util.Properties;

import org.apache.maven.model.Model;
import org.apache.maven.model.Profile;
import org.apache.maven.model.resolution.ModelResolver;
import org.apache.maven.model.resolution.WorkspaceModelResolver;

/**

        builder.clusterTimeout("90s");
        assertEquals("90s", builder.timeoutSettings.clusterTimeout);
    }

    @Test
    public void testBuildWithDefaults() {
        // Test building with default values
        String id = "test-id";
        SuggestSettings settings = builder.build(client, id);

        assertNotNull(settings);

import org.apache.maven.lifecycle.internal.ReactorContext;
import org.apache.maven.lifecycle.internal.TaskSegment;

/**
 * <p>
 * A {@link Builder} encapsulates a strategy for building a set of Maven projects. The default strategy in Maven builds
 * the projects serially, but a {@link Builder} can employ any type of concurrency model to build the projects.
 * </p>

 *
 * Doing it correctly would require running a Gradle build with the full
 * distribution and extracting the generated api jar from its Gradle user home,
 * slowing down building documentation.
 *
 * All this would be so much simpler if the Kotlin extensions to the Gradle API
 * were generated at build time instead.
 *
 * This is a first step to get the doc to be complete and will be revisited.