Third-Party Licenses

Commander incorporates third-party components (including Free and Open-Source Software, or FOSS) whose licenses require us to publish copies of the licensing language and/or copyright notices. In compliance with those requirements, here are links to copies of the licenses.

Apache 2.0 License

License

Tools incorporated in Commander that use this license

Common Development and Distribution License

Tools incorporated in Commander that use this license

Common Public License

Tools incorporated in Commander that use this license

Eclipse Public License 1.0

Tools incorporated in Commander that use this license

Eclipse Distribution License 1.0

Tools incorporated in Commander that use this license

GNU Lesser General Public License

Tools incorporated in Commander that use LGPL version 3

Tools incorporated in Commander that use LGPL version 2.1

Tools incorporated in Commander that use LGPL version 2

Tools incorporated in Commander that use an unspecified version of LGPL

BSD

Tools incorporated in Commander that use this license

BSD-3

Tools incorporated in Commander that use this license

Mozilla Public License

Tools incorporated in Commander that use this license

MIT License

Tools incorporated in Commander that use this license

Tool-specific licenses

Tool

License

Ace

License

Bouncy Castle

License (This should be read in the same way as the MIT License)

dom4j

License

esapi-2.0.1.jar

License

icu4j

License

jaxen

License

JSch

License

JWbem

License

JZlib

License

PostgreSQL

License

Stax-utils

License

user-agent-utils

License

xpp3_min

License

XStream

License


In testing its products, and in particular their interactions with other vendors' products (e.g., Microsoft Windows, SQL Server), Snow Software (“Snow”) uses default installations of the supported versions and editions of these third-party products, configured as per the Snow System Requirements document.

Many of these third-party products offer additional features and configuration options. Please refer to each third-party product's documentation for details.

These additional third-party product features and configurations are not tested by Snow for compatibility purposes, and unless otherwise stated might have an impact on the functionality and performance of Snow products.

Snow products may not operate in accordance with the applicable Snow product documentation in environments where these additional third-party features and configurations are implemented.

For these reasons, any implementation of such additional third-party product features and configurations must be validated by the installation's technical owner(s) on a case-by-case basis and implemented under their responsibility.

As best practices would suggest, a preliminary implementation on an expendable test environment and a complete backup and restore strategy are highly recommended before any such implementation of third-party product features.