* under the License.
 */
package org.apache.maven.api.services;

/**
 * The transformerContextBuilder is responsible for initializing the TransformerContext.
 * In case rawModels are missing, it could do new buildingRequests on the ModelBuilder.
 *
 * @since 4.0.0
 */
public interface ModelTransformerContextBuilder {
    /**
     * This method is used to initialize the TransformerContext
     *

contribution quickly and easily:

 - [ ] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/MNG) filed
       for the change (usually before you start working on it).  Trivial changes like typos do not
       require a JIRA issue. Your pull request should address just this issue, without
       pulling in other changes.
 - [ ] Each commit in the pull request should have a meaningful subject line and body.

     */
    default void validateFileModel(Model model, ModelBuilderRequest request, ModelProblemCollector problems) {
        // do nothing
    }

    /**
     * Checks the specified (raw) model for missing or invalid values. The raw model is the file model + buildpom filter

        Activation activation = profile.getActivation();

        String jdk = activation.getJdk();

        // null case is covered by canDetermineActivation(), so we can do a straight startsWith() here.
        if (jdk.startsWith("[") || jdk.startsWith("(")) {
            try {
                return matchJdkVersionRange(jdk);
            } catch (InvalidVersionSpecificationException e) {

            } else {
                unresolvedOptionalSelectors.add(selector);
            }
        }

        if (!unresolvedOptionalSelectors.isEmpty()) {
            LOGGER.info("The requested optional projects {} do not exist.", unresolvedOptionalSelectors);
        }

        return resolvedOptionalProjects;
    }

    private List<MavenProject> getChildProjects(MavenProject parent, MavenExecutionRequest request) {

        if (!VALID_MODEL_VERSIONS.contains(superModelVersion)) {
            // Maven 3.x is always using 4.0.0 version to load the supermodel, so
            // do the same when loading a dependency.  The model validator will also
            // check that field later.
            superModelVersion = "4.0.0";
        }

                        try {
                            ResolutionGroup rGroup;

                            Object childKey;
                            do {
                                childKey = child.getKey();

                                if (managedVersions.containsKey(childKey)) {

import org.slf4j.LoggerFactory;

@Singleton
@Named
public final class DefaultPluginValidationManager extends AbstractEventSpy implements PluginValidationManager {
    /**
     * The collection of "G:A" combinations that do NOT belong to Maven Core, hence, should be excluded from
     * "expected in provided scope" type of checks.
     */
    static final Collection<String> EXPECTED_PROVIDED_SCOPE_EXCLUSIONS_GA =

    sensitive the online state of the application, and that this state is
    currently wrong for execution.

    <<NOTE:>> Do we want to fail when we cannot bind a mojo to the lifecycle
    because of offline/online status? That would probably indicate that the user
    was trying to do something they cannot succeed at for now...so we probably

                final PrintStream projectStream = printStreams.get(projectBuild);
                ByteArrayOutputStream projectOs = streams.get(projectBuild);

                do {
                    synchronized (projectStream) {
                        try {
                            projectStream.wait(100);
                        } catch (InterruptedException e) {