import org.apache.maven.api.spi.ModelParserException;

/**
 * Collects problems that are encountered during model building. The primary purpose of this component is to account for
 * the fact that the problem reporter has/should not have information about the calling context and hence cannot provide
 * an expressive source hint for the model problem. Instead, the source hint is configured by the model builder before

            throws MisconfiguredToolchainException {
        List<ToolchainPrivate> toRet = new ArrayList<>();

        ToolchainFactory fact = factories.get(type);
        if (fact == null) {
            logger.error("Missing toolchain factory for type: " + type + ". Possibly caused by misconfigured project.");
        } else {
            List<ToolchainModel> availableToolchains =

Build-Jdk: 1.6.0_07 META-INF/maven/org.apache.maven.its/a/pom.xml 4.0.0 org.apache.maven.its a 0.1 jar Maven Integration Test :: Dummy Artifact maven-core-it file:///${basedir}/repo META-INF/maven/org.apache.maven.its/a/pom.properties #Generated by Maven #Sat Oct 24 00:27:56 CEST 2009 version=0.1 groupId=org.apache.maven.its artifactId=a...

testing of Maven core. 2009 maven-core-it file:///${basedir}/repo true true org.apache.maven maven-plugin-api 2.0 . pom.xml src/** src/main/resources META-INF/maven/org.apache.maven.plugins/maven-surefire-plugin/pom.properties #Generated by Maven #Sat Oct 24 00:51:24 CEST 2009 version=0.1 groupId=org.apache.maven.plugins artifactId=maven-surefire-plugin...

assist testing of Maven core. 2009 maven-core-it file:///${basedir}/repo true true org.apache.maven maven-plugin-api 2.0 . pom.xml src/** src/main/resources META-INF/maven/org.apache.maven.plugins/maven-jar-plugin/pom.properties #Generated by Maven #Sat Oct 24 01:24:54 CEST 2009 version=0.1 groupId=org.apache.maven.plugins artifactId=maven-jar-plugin...

     * to the module-path if it contains a {@code module-info.class}, or to the class-path otherwise.
     * For the test output directory, the rules are more complex and are governed by the fact that
     * Java does not accept the placement of two modules of the same name on the module-path.
     * So the modular test output directory usually needs to be placed in a {@code --path-module} option.
     *
     * <ul>

Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor...

     * to the module-path if it contains a {@code module-info.class}, or to the class-path otherwise.
     * For the test output directory, the rules are more complex and are governed by the fact that
     * Java does not accept the placement of two modules of the same name on the module-path.
     * So the modular test output directory usually needs to be placed in a {@code --path-module} option.
     *
     * <ul>