import jcifs.internal.smb1.ServerMessageBlock;

/**
 * SMB1 Delete Directory request message.
 *
 * This command is used to delete a directory on the server.
 * The directory must be empty before it can be deleted.
 */
public class SmbComDeleteDirectory extends ServerMessageBlock {

    /**
     * Creates a new SMB1 delete directory request.
     *
     * @param config the CIFS configuration

import org.apache.maven.plugin.version.PluginVersionResolutionException;

/**
 * <p>
 * Calculates the task segments in the build
 * </p>
 * <strong>NOTE:</strong> This class is not part of any public api and can be changed or deleted without prior notice.
 *
 * @since 3.0
 */
public interface LifecycleTaskSegmentCalculator {
    List<TaskSegment> calculateTaskSegments(MavenSession session)

import java.util.List;

/**
 * Describes the required task segment as provided on the maven command line; i.e. "clean jetty:run install"
 *
 * <strong>NOTE:</strong> This class is not part of any public api and can be changed or deleted without prior notice.
 *
 * @since 3.0
 */
public final class TaskSegment {

    // Can be both "LifeCycleTask" (clean/install) and "GoalTask" (org.mortbay.jetty:maven-jetty-plugin:6.1.19:run)

import org.apache.maven.plugin.MojoExecution;
import org.apache.maven.project.MavenProject;

/**
 * <strong>NOTE:</strong> This class is not part of any public api and can be changed or deleted without prior notice.
 * @since 3.0
 */
public class PhaseRecorder {
    private String lastLifecyclePhase;

    private final MavenProject project;

    public PhaseRecorder(MavenProject project) {

 * have the support necessary to guarantee that it is not vulnerable to race conditions that would
 * allow it to delete files and directories outside of the directory being deleted (i.e., {@link
 * SecureDirectoryStream} is not supported).
 *
 * <p>{@link RecursiveDeleteOption#ALLOW_INSECURE} can be used to force the recursive delete method
 * to proceed anyway.
 *

        }
    }

    @Override
    public void deleteObject(final String objectName) {
        try {
            final boolean deleted = storage.delete(BlobId.of(bucket, objectName));
            if (!deleted && logger.isDebugEnabled()) {
                logger.debug("Object may not exist: {}", objectName);
            }
        } catch (final Exception e) {

        ServerMessageBlock request = new SmbComOpenAndX("testfile.txt", 0x01, 0, null);
        ServerMessageBlock response = new SmbComOpenAndXResponse();

        // Simulate network name deleted error
        SmbException networkDeletedError = new SmbException(SmbException.NT_STATUS_NETWORK_NAME_DELETED, false);

       the task as up-to-date, because these two files, which are based on
       the generated index.xml, are outputs, not inputs. We can be sure of
       this because they are deleted in the @BeforeEach method of the
       OsgiTest test class.

       - To enable the benefit of incremental builds, we can ask Gradle
       to ignore these two files when considering whether the classpath

import org.apache.maven.project.MavenProject;

/**
 * <p>
 * Context of dependency artifacts for a particular project.
 * </p>
 * <strong>NOTE:</strong> This class is not part of any public api and can be changed or deleted without prior notice.
 *
 * @since 3.0
 */
// TODO From a concurrency perspective, this class is not good. The combination of mutable/immutable state is not nice
public class DependencyContext {

import org.apache.maven.project.MavenProject;

/**
 * <p>
 * Provides the positional index of the project
 * </p>
 * <strong>NOTE:</strong> This class is not part of any public api and can be changed or deleted without prior notice.
 *
 * @since 3.0
 */
// TODO Kristian wonders if this class really is necessary and if it overlaps other concepts.
public final class ProjectIndex {