{@code partner}
            (directly synced from a partner Maven 2 repository), {@code deployed} (was deployed from a Maven 2
            instance), {@code verified} (has been hand verified as correct and final).
          </description>
          <required>false</required>
          <type>String</type>
        </field>
      </fields>
    </class>
    <class>

import org.apache.maven.lifecycle.internal.MojoExecutor;
import org.junit.jupiter.api.Test;

import static org.junit.jupiter.api.Assertions.assertNotNull;

/**
 * Just asserts that it's able to create those components. Handy when CDI container gets a nervous breakdown.
 *
 */
class LifecycleExecutorSubModulesTest extends AbstractCoreMavenComponentTestCase {
    @Inject
    private DefaultLifecycles defaultLifeCycles;

    @Inject

          <name>proxies</name>
          <version>1.0.0+</version>
          <description>
            Configuration for different proxy profiles. Multiple proxy profiles
            might come in handy for anyone working from a notebook or other
            mobile platform, to enable easy switching of entire proxy
            configurations by simply specifying the profile id, again either from

         * other specified dependency, will be subject to dependency collection/resolution, i.e. should have an artifact
         * descriptor and a corresponding artifact file. The root artifact on the other hand is only used
         * as a label for the root node of the graph in case no root dependency was specified. As such, the configured
         * root artifact is ignored if {@link #root(DependencyCoordinate)} has been set.
         *