want to analyze the set of transitive dependencies, in particular during early lifecycle phases where
            full dependency resolution might fail due to projects which haven't been built yet.
          </description>
        </field>
        <field>
          <name>dependencyCollection</name>
          <version>2.0.0+</version>

        ArtifactResolutionResult result = resolve(request);

        // We have collected all the problems so let's mimic the way the old code worked and just blow up right here.
        // That's right lets just let it rip right here and send a big incomprehensible blob of text at unsuspecting
        // users. Bad dog!

        resolutionErrorHandler.throwErrors(request, result);

        return result;
    }

clean, aggr and install. "aggr" is an aggregating task while clean and install are lifecyclephases.
There will be three items in the task list for this dataset.

The stubs also exist at different "levels", where one test might wire stubs into a specific live implementation.
In the next test that same "live implementation" will be used in a stub version instead.

Not all live services have stubs, but can be added as needed.
</body>

                    Iterator<Item> left = iterator();
                    Iterator<Item> right = ((ListItem) item).iterator();

                    while (left.hasNext() || right.hasNext()) {
                        Item l = left.hasNext() ? left.next() : null;
                        Item r = right.hasNext() ? right.next() : null;

                        // if this is shorter, then invert the compare and mul with -1

static int indexOfAny(String, String[]); public static int lastIndexOfAny(String, String[]); public static String substring(String, int); public static String substring(String, int, int); public static String left(String, int); public static String right(String, int); public static String mid(String, int, int); public static String[] split(String); public static String[] split(String, String); public static String[] split(String, String, int); public static String concatenate(Object[]); public static...

static int indexOfAny(String, String[]); public static int lastIndexOfAny(String, String[]); public static String substring(String, int); public static String substring(String, int, int); public static String left(String, int); public static String right(String, int); public static String mid(String, int, int); public static String[] split(String); public static String[] split(String, String); public static String[] split(String, String, int); public static String concatenate(Object[]); public static...

static int indexOfAny(String, String[]); public static int lastIndexOfAny(String, String[]); public static String substring(String, int); public static String substring(String, int, int); public static String left(String, int); public static String right(String, int); public static String mid(String, int, int); public static String[] split(String); public static String[] split(String, String); public static String[] split(String, String, int); public static String concatenate(Object[]); public static...

import org.eclipse.aether.RepositorySystemSession;
import org.eclipse.aether.repository.RemoteRepository;
import org.slf4j.LoggerFactory;

// TODO the antrun plugin has its own configurator, the only plugin that does. might need to think about how that works
// TODO remove the coreArtifactFilterManager

/**
 * DefaultBuildPluginManager
 */
@Named
@Singleton
public class DefaultBuildPluginManager implements BuildPluginManager {

        try {
            validateLocalRepository(request);
        } catch (IOException e) {
            return addExceptionToResult(result, e);
        }

        //
        // We enter the session scope right after the MavenSession creation and before any of the
        // AbstractLifecycleParticipant lookups
        // so that @SessionScoped components can be @Injected into AbstractLifecycleParticipants.
        //

    <exportedPackage>jakarta.inject.*</exportedPackage>
    <exportedPackage>jakarta.annotation.*</exportedPackage>

    <!--
      | We may potentially want to export these, but right now I'm not sure that anything Guice specific needs
      | to be made available to plugin authors. If we find people are getting fancy and want to take advantage of