void applyResumptionProperties(MavenExecutionRequest request, Properties properties) {
        String str1 = request.getResumeFrom();
        if (properties.containsKey(REMAINING_PROJECTS) && !(str1 != null && !str1.isEmpty())) {
            String propertyValue = properties.getProperty(REMAINING_PROJECTS);
            Stream.of(propertyValue.split(PROPERTY_DELIMITER))
                    .filter(str -> str != null && !str.isEmpty())

                .map(project -> project.getGroupId() + ":" + project.getArtifactId())
                .collect(Collectors.toList());

        if (remainingProjects.isEmpty()) {
            LOGGER.info("No remaining projects found, resuming the build would not make sense.");
            return Optional.empty();
        }

        return Optional.of(new BuildResumptionData(remainingProjects));
    }

            return getProjectAExecutionPlan();
        }
        if (project.equals(ProjectDependencyGraphStub.B)) {
            return getProjectBExecutionPlan();
        }
        // The remaining are basically "for future expansion"
        List<MojoExecution> me = new ArrayList<>();
        me.add(createMojoExecution("resources", "default-resources", PROCESS_RESOURCES));

  * Not all "remote" repositories will fail. Specifically, if the remote
    repo uses the file:// protocol, and it doesn't refer to a shared
    filesystem, it will continue to be available.

  The question remaining is: Which level of offline mode will we support? It
  seems reasonable to assume that users will be able to tell when localhost is
  not active (in most cases, localhost should be available, even if the rest of

        } catch (AuthorizationException e) {
            throw new TransferFailedException("Authorization failed: " + e.getMessage(), e);
        } finally {
            // Remove remaining TransferListener instances (checksum handlers removed in above finally clause)
            if (downloadMonitor != null) {
                wagon.removeTransferListener(downloadMonitor);
            }

<pre>assertThat(cheese, is(smelly))</pre> * instead of: * <pre>assertThat(cheese, is(equalTo(smelly)))</pre> */ public static <T> org.hamcrest.Matcher<T> is(T value) { return org.hamcrest.core.Is.<T>is(value); } /** * Decorates another Matcher, retaining its behaviour, but allowing tests * to be slightly more expressive. * <p/> * For example: * <pre>assertThat(cheese, is(equalTo(smelly)))</pre> * instead of: * <pre>assertThat(cheese, equalTo(smelly))</pre> */ public static <T> org.hamcrest.Matcher<T>...

Class.isInstance(Object) method on that type, passing the the examined object. Is<T> - Class in org.hamcrest.core Decorates another Matcher, retaining the behaviour but allowing tests to be slightly more expressive. Is(Matcher<T>) - Constructor for class org.hamcrest.core.Is is(Matcher<T>) - Static method in class org.hamcrest.core.Is Decorates another Matcher, retaining its behaviour, but allowing tests to be slightly more expressive. is(T) - Static method in class org.hamcrest.core.Is A shortcut to the...

         * Filters the types of paths to include in the result.
         * The result will contain only the paths of types for which the predicate returned {@code true}.
         * It is recommended to apply a filter for retaining only the types of paths of interest,
         * because it can resolve ambiguities when a path could be of many types.
         *

                    versioning.setLastUpdated(now);
                    changed = true;
                }
            }
        }

        if (changed) {
            getLogger().debug("Repairing metadata in " + metadataFile);

            try (OutputStream out = Files.newOutputStream(metadataFile.toPath())) {
                new MetadataStaxWriter().write(out, metadata.getDelegate());