import org.slf4j.Logger;
import org.slf4j.LoggerFactory;

/**
 * Provides basic services to manage Maven plugins and their mojos. This component is kept general in its design such
 * that the plugins/mojos can be used in arbitrary contexts. In particular, the mojos can be used for ordinary build
 * plugins as well as special purpose plugins like reports.
 *
 * @since 3.0
 */
@Named
@Singleton

        debugDependencyRequirements(executionPlan.getMojoExecutions());

        logger.debug("Repositories (dependencies): " + currentProject.getRemoteProjectRepositories());
        logger.debug("Repositories (plugins)     : " + currentProject.getRemotePluginRepositories());

        for (ExecutionPlanItem mojoExecution : executionPlan) {
            debugMojoExecution(mojoExecution.getMojoExecution());
        }

        addGAVElements(dependency, groupId, artifactId, version);
        return dependency;
    }

    /**
     * Convenience method to create a plugin element with GAV.
     *
     * @param pluginsElement the plugins parent element
     * @param groupId the groupId value
     * @param artifactId the artifactId value
     * @param version the version value (can be null)
     * @return the created plugin element
     *
     */

 * [okhttp-client-mock](https://github.com/gmazzo/okhttp-client-mock): A simple OKHttp client mock, using a programmable request interceptor.
 * [OkHttp Profiler](https://plugins.jetbrains.com/plugin/11249-okhttp-profiler): An IntelliJ plugin for monitoring OkHttp calls.
 * [OkReplay](https://github.com/airbnb/okreplay): Record and replay OkHttp network interaction in your tests.

        this.configurationElement = element;
        return this;
    }

    /**
     * Sets the configuration to the configuration taken from the specified build plugin in the POM. First, the build
     * plugins will be searched for the specified plugin, if that fails, the plugin management section will be searched.
     *
     * @param model The POM to extract the plugin configuration from, may be {@code null}.

            The lists of the remote repositories for discovering plugins.
          </description>
          <association>
            <type>Repository</type>
            <multiplicity>*</multiplicity>
          </association>
          <comment>
            This may be removed or relocated in the near
            future. It is undecided whether plugins really need a remote
            repository set of their own.

~~ TODO document META-INF/maven/slf4j-configuration.properties

* Getting Logger Instance

 Starting with Maven 3.1.0, SLF4J Logger can be used directly. This technique can be used safely in Maven core
 components or in plugins/component not requiring compatibility with previous Maven versions.

+-----+
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;

public class MyClass
{

     * {@link Session#resolveDependencies resolveDependencies(...)} when at least one dependency
     * cannot be associated to any type specified in the {@code desiredTypes} argument.
     * Plugins can choose to report a warning to users when unresolved paths exist.
     */
    PathType UNRESOLVED = new PathType() {
        @Override
        public String name() {
            return "UNRESOLVED";
        }

```console
$ pytest

================ test session starts ================
platform linux -- Python 3.6.9, pytest-5.3.5, py-1.8.1, pluggy-0.13.1
rootdir: /home/user/code/superawesome-cli/app
plugins: forked-1.1.3, xdist-1.31.0, cov-2.8.1
collected 6 items

---> 100%

test_main.py <span style="color: green; white-space: pre;">......                            [100%]</span>

        writer.accept("Project:                     " + getKey(project));
        writer.accept("Repositories (dependencies): " + project.getRemoteProjectRepositories());
        writer.accept("Repositories (plugins):      " + project.getRemotePluginRepositories());

        Optional<BuildStep> planStep = plan.step(project, BuildStep.PLAN);
        if (planStep.isPresent() && planStep.get().status.get() == BuildStep.PLANNING) {