result = false;
                        break;
                    }
                }
                // check for exact match
                else if (repo.equals(originalId)) {
                    result = true;
                    break;
                }
                // check for external:*
                else if (EXTERNAL_WILDCARD.equals(repo) && isExternalRepo(originalRepository)) {

<!DOCTYPE suppressions PUBLIC
        "-//Checkstyle//DTD SuppressionFilter Configuration 1.0//EN"
        "https://checkstyle.org/dtds/suppressions_1_0.dtd">

<suppressions>
    <suppress checks="JavadocVariable|JavadocMethod" files=".*" />
    <suppress checks="HiddenField" files=".*" />

import org.apache.maven.api.model.Model;
import org.apache.maven.api.services.ModelBuilderRequest;
import org.apache.maven.api.services.ModelProblemCollector;

/**
 * Checks the model for missing or invalid values.
 *
 */
public interface ModelValidator {
    /**
     * Checks the specified file model for missing or invalid values. This model is directly created from the POM

     * Retrieves the current Maven version, for example "3.0.2".
     *
     * @return The current Maven version or an empty string if unknown, never {@code null}.
     */
    String getMavenVersion();

    /**
     * Checks whether the current Maven runtime matches the specified version range. A version range can either use the
     * usual mathematical syntax "[2.0.10,2.1.0),[3.0,)" or use a single version "2.2.1". The latter is a short form for

     * @throws VersionParserException if the range specification violates the syntax rules of this scheme
     */
    @Nonnull
    VersionConstraint parseVersionConstraint(@Nonnull String constraint);

    /**
     * Checks whether a given artifact version is considered a {@code SNAPSHOT} or not.
     */
    boolean isSnapshot(@Nonnull String version);

 - [ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
 - [ ] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will
       be performed on your pull request automatically.
 - [ ] You have run the [Core IT][core-its] successfully.

If your pull request is about ~20 lines of code you don't need to sign an

    Test that POM parsing properly coalesces text data.
  </description>

  <properties>
    <!--
    This checks the coalescing of CHARACTERS and CDATA events. Note that inner whitespace must be retained.
    -->
    <prop0>A <![CDATA[ Test ]]> Project<![CDATA[ ]]>Property</prop0>

    <!--
    This checks the coalescing of CHARACTERS events that are interleaved with comments. Note that inner whitespace

     * @throws VersionParserException if the range specification violates the syntax rules of this scheme
     */
    @Nonnull
    VersionConstraint parseVersionConstraint(@Nonnull String constraint);

    /**
     * Checks whether a given artifact version is considered a {@code SNAPSHOT} or not.
     */
    boolean isSnapshot(@Nonnull String version);

 *   <li>file system errors: permissions</li>
 * </ul>
 *
 * TODO carlos: all these possible has*Exceptions and get*Exceptions methods make the clients too
 *       complex requiring a long list of checks, need to create a parent/interface/encapsulation
 *       for the types of exceptions
 */
@Deprecated
public class ArtifactResolutionResult {
    private static final String LS = System.lineSeparator();

    /**
     * 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 =
            Collections.unmodifiableCollection(Arrays.asList(