* overriding going on amongst the models being used in this test:
 * each model in the lineage is providing a value that is not present
 * anywhere else in the lineage. We are just making sure that values
 * down in the lineage are bubbling up where they should.
 *
 */
@Deprecated
class ProjectInheritanceTest extends AbstractProjectInheritanceTestCase {
    // ----------------------------------------------------------------------

  <packaging>jar</packaging>

  <name>Maven Integration Test :: MNG-4107</name>
  <description>
    Test that POM interpolation uses the property values from the dominant profile source (POM vs. settings.xml).
    This boils down to the proper order of profile injection and interpolation, i.e.
    interpolate after profiles from all sources are injected.
  </description>

  <properties>

            url = "file://" + url.substring("file:".length());
        }

        // So now we have an url of the form file://<path>

        // We want to eliminate any relative path nonsense and lock down the path so we
        // need to fully resolve it before any submodules use the path. This can happen
        // when you are using a custom settings.xml that contains a relative path entry

import org.eclipse.sisu.EagerSingleton;
import org.eclipse.sisu.PreDestroy;

import static java.util.Objects.requireNonNull;

/**
 * Maven internal component that bridges container "shut down" to {@link RepositorySystem#shutdown()}.
 *
 * @since 3.9.0
 */
@Named
@EagerSingleton
final class ResolverLifecycle {
    private final Provider<RepositorySystem> repositorySystemProvider;

    @Inject

 * overriding going on amongst the models being used in this test:
 * each model in the lineage is providing a value that is not present
 * anywhere else in the lineage. We are just making sure that values
 * down in the lineage are bubbling up where they should.
 *
 */
@Deprecated
class ProjectInheritanceTest extends AbstractProjectInheritanceTestCase {
    // ----------------------------------------------------------------------

        for (Plugin plugin : project.getBuild().getPlugins()) {
            for (PluginExecution execution : plugin.getExecutions()) {
                // if the phase is specified then I don't have to go fetch the plugin yet and pull it down
                // to examine the phase it is associated to.
                if (execution.getPhase() != null) {
                    Map<Integer, List<MojoExecution>> phaseBindings = mappings.get(execution.getPhase());

        <forkId implementation="int" default-value="-1">${forkId}</forkId>
      </configuration>
    </mojo>
    <mojo>
      <goal>clear-fork-context</goal>
      <description>Tear down any build state used during the previous forked execution.</description>
      <requiresDirectInvocation>false</requiresDirectInvocation>
      <requiresProject>false</requiresProject>
      <requiresReports>false</requiresReports>

  repositories are "really" offline, since offline mode is more of a behavior,
  and this will lead to counter-intuitive results. A different feature may exist
  unimplemented, which is to detect when the network is down and provide better
  feedback for that case. However, when offline mode is declared, nothing
  earmarked as remote should be accessed, regardless of whether it is actually
  a physically local resource.

matcher for argument <var>item</var>. * <p/> * This method matches against Object, instead of the generic type T. This is * because the caller of the Matcher does not know at runtime what the type is * (because of type erasure with Java generics). It is down to the implementations * to check the correct type. * * @param item the object against which the matcher is evaluated. * @return <code>true</code> if <var>item</var> matches, otherwise <code>false</code>. * * @see BaseMatcher */ boolean matches(Object...

  <artifactId>plexus-components</artifactId>
  <packaging>pom</packaging>
  <version>1.1.6</version>
  <name>Plexus Components Parent Project</name>
  <!--
    TODO: should this be pushed down to all the dependencies?
      - a more stable API JAR may be useful, for the interfaces and classes such as AbstractLogEnabled
  -->
  <dependencies>
    <dependency>
      <groupId>org.codehaus.plexus</groupId>