HiveMQ 2.1.0 is out & HiveMQ Artifacts are in Maven Central
Written by HiveMQ Team
Category: HiveMQ Release
Published: September 25, 2014
We are very excited to announce the next minor version of HiveMQ, HiveMQ 2.1.0. We added many new features and squashed some bugs.
Improvements in the plugin system
We improved the HiveMQ Open Source Plugin System, which now isolates the classpath of each plugin. This makes sure that libraries or classes used in the plugins can not interfere with the HiveMQ core in a non-expected way and you can write different plugins with different Java libraries without interfering. This also makes sure, you don’t accidentally inject resources from other plugins via dependency injection.
Last Will and Testament Behavior
Another new feature is, that the Last Will and Testament behavior is now configurable. This enables HiveMQ to send a LWT message even if the client disconnected gracefully. The HiveMQ default complies to the MQTT specification and only sends the LWT when the disconnect is not gracefully. To enable this feature, just set the following property in the configuration.properties file:
TLS for bridges
Since version 2.0.0 HiveMQ fully supports the MQTT bridge protocol. From now on bridges also work with SSL/TLS transport encryption and client certificate authentication. You can read more about the configuration of bridges in the official user guide.
HiveMQ artifacts in Maven Central
We also finally pushed our HiveMQ SPI, the HiveMQ Maven Plugin and the HiveMQ Plugin Archetype to Maven Central. This means writing a plugin has just become even more simple, because the need for using our Maven Repository for plugin devleopment becomes obsolete.
Now you can just use the plugin archetype to get started with developing your own HiveMQ plugin. The following command gets you a fully functioning Hello World plugin to start right away.
For further instruction about plugin development, see our plugin developer guide.
Apart from that there have been a number of rather small bugfixes and improvements. For a full list see the 2.1.0 changelog.
Everybody is adviced to upgrade to this new version, which is a drop-in replacement for HiveMQ 2.0.x.
We’re always open to feedback and try to make HiveMQ better every single day. So tell us what you like or maybe don’t like in the comments, our support forum or via e-mail.
The HiveMQ Team