Starting today, the nightly builds will be signed with a new certificate. This may cause a warning or prompt to reverify that you want to run software signed with the new certificate. The latest release build is still signed with the old certificate and will stay that way until the next release.
I’ve been working on Message Manager 3.0, which will replace the 2.x branch Sonic Message Manager in time. This will be a separate download and will not automatically upgrade from 2.x versions for technical reasons. There are major changes in the application, but most of those are invisible to the users:
The first beta version of 3.0 is available for download here. These versions will automatically update to the latest code on a nightly basis and should be considered unstable.
The source code for this version is available on Bitbucket, please report any issues here.
Future versions of Message Manager 3.0 will no longer be specific to a particular version of Sonic MQ. At that time, you will have to download a new version of the application.
I’ve obtained a new code signing certificate and used it to sign the nightly builds. Since this is a new certificate, you may see error messages if Java Web Start was unable to update all downloaded files at once. If you get a message stating that “Not all files are signed with the same certificate” or “The signed version does not match the downloaded version”, clear your Java Web Start cache and try again.
In rare cases, Java Web Start may get stuck and there is no way to fix it. In that case, you will have to resort the stable builds or offline installation for 24h to give Java Web Start some time to realize that it needs to update the rest of the files.