* This interface allows plugins and extensions to define and register additional build lifecycles
 * beyond the standard ones provided by Maven (like clean, default, site). Lifecycles define a sequence
 * of phases that can be executed during a build.
 * <p>
 * Implementations of this interface will be discovered through the Java ServiceLoader mechanism
 * and their provided lifecycles will be available throughout the Maven build process.
 * <p>
 * Example usage:

 * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
 */
package jcifs.util.transport;

/**
 * Exception thrown when a network connection times out during SMB communication.
 * Indicates that the connection could not be established within the specified timeout period.
 *
 * @author mbechler
 */
public class ConnectionTimeoutException extends TransportException {

     */
    public MimeTypeException(final String message, final Throwable cause) {
        super(message, cause);
    }

    /**
     * Creates a new MimeTypeException with the specified detail message.
     *
     * @param message the detail message explaining the reason for the exception
     */
    public MimeTypeException(final String message) {
        super(message);
    }

    /**

 * specific language governing permissions and limitations
 * under the License.
 */
package org.apache.maven.execution;

/**
 * Defines events that Maven fires during a build. <strong>Warning:</strong> This interface might be extended in future
 * Maven versions to support further events. Hence it is strongly recommended to derive custom listeners from

import gradlebuild.testcleanup.extension.TestFilesCleanupProjectState

/**
 * When run from a Continuous Integration environment, we only want to archive a subset of reports, mostly for
 * failing tasks only, to not use up unnecessary disk space on Team City. This also improves the performance of
 * artifact publishing by reducing the artifacts and packaging reports that consist of multiple files.
 *

- [ ] Provide unit tests (under `<subproject>/src/test`) to verify logic.
- [ ] Update User Guide, DSL Reference, and Javadoc for public-facing changes.
- [ ] Ensure that tests pass sanity check: `./gradlew sanityCheck`.
- [ ] Ensure that tests pass locally: `./gradlew <changed-subproject>:quickTest`.

### Reviewing cheatsheet

@DisplayName("Smb2SessionSetupResponse Tests")
@MockitoSettings(strictness = Strictness.LENIENT)
class Smb2SessionSetupResponseTest extends BaseTest {

    private Smb2SessionSetupResponse newResponse() {
        // Configuration is not used during decode when no signing digest is set
        Configuration cfg = mock(Configuration.class);
        return new Smb2SessionSetupResponse(cfg);
    }

    /**

        } else {
            trackingDir = event.getFile().getParentFile().toPath().resolve(".tracking");
        }

        String baseName;
        String ext = missing ? ".miss" : ".dep";
        Path trackingFile = null;

        StringBuilder indent = new StringBuilder();
        ArrayList<String> trackingData = new ArrayList<>();

        if (collectStepTrace == null && plugin != null) {
            ext = ".plugin";

know how to find the dependencies of a plugin whether that be from a workspace of an IDE, a local Maven repository, or a remote Maven repository. During development in an IDE we would need layered resolution approach that would allow resolution from the workspace, then the local Maven repository and then from any number of remote Maven repositories. During development from the command line we would need a layered resolution approach that would allow resolution from the local Maven repository and then...

            System.err.println("An error occurred during verification: " + e.getMessage());
            throw new RuntimeException("Error during file verification", e);
        }
    }

    private static class AdocFileEntry {
        @SerializedName("filename")
        String filename;
        @SerializedName("anchors")
        List<String> anchors;
    }

    /**