- [Other notable changes](#other-notable-changes)
- [v1.14.9](#v1149)
  - [Downloads for v1.14.9](#downloads-for-v1149)
    - [Client Binaries](#client-binaries-1)
    - [Server Binaries](#server-binaries-1)
    - [Node Binaries](#node-binaries-1)
  - [Changelog since v1.14.8](#changelog-since-v1148)
    - [Other notable changes](#other-notable-changes-1)
- [v1.14.8](#v1148)

/**
 * Enumeration of SMB Witness Event Types as defined in MS-SWN specification.
 * These events represent different types of cluster state changes that clients
 * can be notified about.
 */
public enum WitnessEventType {
    /**
     * Resource state changed - general resource state modification
     */
    RESOURCE_CHANGE(1),

    /**
     * Client should move to different node - directed failover
     */

    - [Node Binaries](#node-binaries-5)
  - [Changelog since v1.19.10](#changelog-since-v11910)
  - [Changes by Kind](#changes-by-kind-5)
    - [API Change](#api-change)
    - [Feature](#feature-3)
    - [Bug or Regression](#bug-or-regression-4)
  - [Dependencies](#dependencies-5)
    - [Added](#added-5)
    - [Changed](#changed-5)
    - [Removed](#removed-5)
- [v1.19.10](#v11910)
  - [Downloads for v1.19.10](#downloads-for-v11910)

   * Registers a {@link Listener} to be {@linkplain Executor#execute executed} on the given
   * executor. The listener will have the corresponding transition method called whenever the
   * service changes state. The listener will not have previous state changes replayed, so it is
   * suggested that listeners are added before the service starts.
   *
   * <p>{@code addListener} guarantees execution ordering across calls to a given listener but not

- Creation and deletion of buckets and objects
- Creation and deletion of all IAM users, groups, policies and their mappings to users or groups
- Creation of STS credentials
- Creation and deletion of service accounts (except those owned by the root user)
- Changes to Bucket features such as:
  - Bucket Policies
  - Bucket Tags

  - [Changes by Kind](#changes-by-kind-9)
    - [API Change](#api-change)
    - [Feature](#feature-6)
    - [Bug or Regression](#bug-or-regression-9)
  - [Dependencies](#dependencies-9)
    - [Added](#added-9)
    - [Changed](#changed-9)
    - [Removed](#removed-9)
- [v1.31.4](#v1314)
  - [Downloads for v1.31.4](#downloads-for-v1314)

  - [Changes by Kind](#changes-by-kind-5)
    - [API Change](#api-change)
    - [Feature](#feature-3)
    - [Bug or Regression](#bug-or-regression-4)
  - [Dependencies](#dependencies-5)
    - [Added](#added-5)
    - [Changed](#changed-5)
    - [Removed](#removed-5)
- [v1.30.8](#v1308)
  - [Downloads for v1.30.8](#downloads-for-v1308)

     * called right before the actual version/artifactScope changes were done. However, a different set of conditionals
     * (and more information) is needed to be able to determine when and if the version and/or artifactScope changes.
     * See the two added methods, manageArtifactVersion and manageArtifactScope.
     */
    @Override

    - [Other notable changes](#other-notable-changes)
- [v1.13.11](#v11311)
  - [Downloads for v1.13.11](#downloads-for-v11311)
    - [Client Binaries](#client-binaries-1)
    - [Server Binaries](#server-binaries-1)
    - [Node Binaries](#node-binaries-1)
  - [Changelog since v1.13.10](#changelog-since-v11310)
    - [Other notable changes](#other-notable-changes-1)
- [v1.13.10](#v11310)

   <version></version>
 </parent>
</project>
+-----+

Extending the POM in the future

  In order to anticipate changes in the structure of the POM as new releases of
  maven occur, the maven inheritance model must be pinned against a particular
  modelVersion. This is required so that a change from modelVersion 4.0.0 to
  4.1.0 doesn't cause compatibility problems with users who have not upgraded