*/
    String getMessage();

    /**
     * Gets the severity level of this problem.
     *
     * @return The severity level of this problem, never {@code null}.
     */
    Severity getSeverity();

    /**
     * Gets the applicable maven version/validation level of this problem
     * @return The version, never {@code null}.
     */
    Version getVersion();

     */
    @Nonnull
    String getMessage();

    /**
     * Gets the severity level of this problem.
     *
     * @return the severity level of this problem, never {@code null}
     */
    @Nonnull
    Severity getSeverity();

    /**
     * The different severity levels for a problem, in decreasing order.
     *
     * @since 4.0.0
     */
    @Experimental
    enum Severity {

 *       <ul>
 *         <li>2 levels: average of 64ns per lock()/unlock()
 *         <li>3 levels: average of 77ns per lock()/unlock()
 *         <li>4 levels: average of 99ns per lock()/unlock()
 *         <li>5 levels: average of 103ns per lock()/unlock()
 *         <li>10 levels: average of 184ns per lock()/unlock()
 *         <li>20 levels: average of 393ns per lock()/unlock()
 *       </ul>
 * </ul>

        /**
         * The information level to return.
         */
        public int level;
        /**
         * The share information.
         */
        public NdrObject info;

        /**
         * Constructs a ShareGetInfo request.
         * @param servername the server name
         * @param sharename the share name
         * @param level the information level

        // Set different levels
        when(basicInfo.getFileInformationLevel()).thenReturn(FileInformation.FILE_BASIC_INFO);
        when(standardInfo.getFileInformationLevel()).thenReturn(FileInformation.FILE_STANDARD_INFO);
        when(internalInfo.getFileInformationLevel()).thenReturn(FileInformation.FILE_INTERNAL_INFO);

        // Verify each has correct level

Since they define the primary structure of the project/build.

The stubs define three top-level targets that are defined in  LifecycleTaskSegmentCalculatorStub;
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.

 *
 * <h2>Repository Configuration</h2>
 *
 * <p>Repositories can be configured at various levels:</p><ol>
 * <li>POM: Repositories can be specified in the {@code pom.xml} file under the {@code <repositories>} and {@code <pluginRepositories>} sections.</li>
 * <li>Settings: the {@code settings.xml} can be used to provide additional repositories in the three level of settings (user, project, installation).</li>
 * </ol>

 *
 * <h2>Repository Configuration</h2>
 *
 * <p>Repositories can be configured at various levels:<ol>
 * <li>POM: Repositories can be specified in the {@code pom.xml} file under the {@code <repositories>} and {@code <pluginRepositories>} sections.</li>
 * <li>Settings: the {@code settings.xml} can be used to provide additional repositories in the three level of settings (user, project, installation).</li>
 * </ol>

    @ParameterizedTest
    @ValueSource(bytes = { FileInformation.FILE_BASIC_INFO, FileInformation.FILE_STANDARD_INFO, FileInformation.FILE_INTERNAL_INFO })
    @DisplayName("Test readDataWireFormat with different information levels")
    void testReadDataWireFormatWithDifferentLevels(byte infoLevel) throws SMBProtocolDecodingException {
        response = new Trans2QueryPathInformationResponse(mockConfig, infoLevel);

        /**
         * The information level to return.
         */
        public int level;
        /**
         * The share information.
         */
        public NdrObject info;

        /**
         * Constructs a ShareGetInfo request.
         * @param servername the server name
         * @param sharename the share name
         * @param level the information level