<dependency> <groupId>org.rxtx</groupId> <artifactId>rxtx</artifactId> <version>2.1.7</version> <scope>provided<scope> </dependency>
The PGP signatures can be verified using PGP or GPG. First download the KEYS as well as the asc signature file for the relevant distribution. Then verify the signatures using:
$ pgpk -a KEYS $ pgpv mina-2.1.6.tar.gz.asc
or
$ pgp -ka KEYS $ pgp mina-2.1.6.tar.gz.asc
or
$ gpg --import KEYS $ gpg --verify mina-2.1.6.tar.gz.asc
Older versions can be found on https://archive.apache.org/dist/mina/
The PGP signatures can be verified using PGP or GPG. First download the KEYS as well as the asc signature file for the relevant distribution. Then verify the signatures using:
$ pgpk -a KEYS $ pgpv mina-2.1.6.tar.gz.asc
or
$ pgp -ka KEYS $ pgp mina-2.1.6.tar.gz.asc
or
$ gpg --import KEYS $ gpg --verify mina-2.1.6.tar.gz.asc
The previous releases can be found on https://archive.apache.org/dist/mina/. Please note that the following releases contains a LGPL licensed file, rxtx-2.1.7.jar: 2.0.0-M4, 2.0.0-M5, 2.0.0-M6, 2.0.0-RC1.
The version number of MINA has the following form:
This scheme has three number components:
and an optional label that indicates the maturity of a release:
MINA is not a stand-alone software, so ‘the feature set’ here also includes the API of the newly introduced features and the overall architecture of the software,
Here's an example that illustrates how MINA version number increases:
Please note that we always specify the micro number, even if it's zero.