Ignite Realtime is the community site for the users and developers of Jive Software's open source Real Time Communications projects. Your involvement is helping to change the open RTC landscape.
Openfire Meetings version 0.1.5 has a new meeting planner feature that enables you to schedule meetings in advance using a calendar.When you add a meeting to the calendar, a request to join the meeting is automatically generated and sent to each participant using Openfire's email service 15 mins before the meeting starts. Included in the email is a link to join the meeting from a Chrome web browser.
In order to use this feature, you will need:
The calendar is implemented using the excellent open source fullcalendar jquery plugin by Adam Shaw.
The Ignite Realtime community has released Spark 2.7.0 for general availability and it can be downloaded from Ignite Realtime: Downloads (Note: there are no working Mac OS X installer as our current build environment has no working setup for Mac, also Spark has lots of issues on the current Mac OS versions and the community has no active Mac OS developers willing to step in).
This release is a mandatory one to use with the recently released Openfire 3.10.0. As 2.6.3 version has issues connecting to the new server version. Though there is a not recommended workaround to revert to using Old SSL setting, which is less secure than TLS. The community strongly advises to upgrade to 2.7.0 version. Even if you are not planning to update to 3.10.0 release of Openfire yet. Spark hasn't seen a release in almost 3 years, but it was constantly evolving. Many fixes and improvements have been applied to the code since the last release. Some users have it deployed in the production environment for years and find it more stable than 2.6.3 version (as myself with 200+ user base).
We are sad that currently Spark has no Project Lead and there are no active contributors to this project. So, fixes and new features may not come up quickly. We hope open source community will embrace and improve this project in the future. You can start sharing your patches on the GitHub. If you find new issues, you can report them in the forums and we will at least file them in the bug tracker for the future developers to tackle.
Here's a list of some important fixes/changes:
[SPARK-1074] Sending part doesnt get a notification about the transfer cancellation - Jive Software Open Source
[SPARK-1362] No confirmation on the sender's part that the file transfer completed - Jive Software Open Source
[SPARK-1397] Fix the displaying of system tray icons - Jive Software Open Source (minor one, but not for such a picky person as i am, Spark icon now looks much nicer)
[SPARK-1414] Chat window is not flashing when receiving new message on Windows 7 64 bit - Jive Software Open Source
[SPARK-1525] Update smack - Jive Software Open Source (huge update for Spark and this is probably the cause why 2.6.3 can't connect to newer Openfire as it uses older Smack library)
[SPARK-1524] Spark is not reconnecting automatically after connection loss - Jive Software Open Source
[SPARK-1546] Spark visually shows that a message is not sent - Jive Software Open Source (one of the most annoying bugs in 2.6.3)
Also the Conversation history dialog has been completely reworked and should load faster and should be easier to navigate. Java has been updated to the recent 1.7.0 version, which should fix issues with some timezones. There are also numerous memory leak fixes. You can find the full changelog here: Spark Changelog
There are also some open issues. Like the still broken voice chat module. One of the past Spark maintainers cstux has started a work on fixing this, but it is moving slowly. File transfers may not work between 2.6.3 and 2.7.0 versions because of many changes to this functionality in 2.7.0. This is a somewhat frightening list of open issues (though many are minor) Spark - Jive Software Open Source So, again, we encourage Java developers to move this project forward.
Here are sha1sums for the downloads:
The Ignite Realtime community is very proud to release Openfire 3.10.0 for general availability from http://www.igniterealtime.org/downloads/
The amount of energy that has gone into this release is truly impressive, and it shows no signs of slowing down - as those of your looking at the 3.11 branch will have seen. Further 3.10.X releases will be bugfix releases; 3.11 will concentrate on a path to 4.0.0.
3.10.0 itself brings new core features to Openfire (such as Message Carbons, for example, by Christian Schudt) and vital improvements (to clustering and MUC, for example, by Tom Evans), as well as some hard bugfixing (by Guus der Kinderen) and important security improvements.
As ever, we welcome pull requests (to 3.10 or master as appropriate), and the entire development team is looking forward to you joining the conversation either in the forums or in the XMPP chatroom at firstname.lastname@example.org
UPDATE: Spark 2.6.3 version has issues with connecting to this version of Openfire. We suggest updating to just released 2.7.0 version of Spark.
The Ignite Realtime Community is pleased to announce a release candidate build of the upcoming 3.10.0 release. A lot of work has gone into this RC since the beta release a few months back and with your help testing, we are hoping to turn around a full 3.10.0 release very soon! Here are some of the highlights since the beta:
For those of you that track our progress on Github, we are starting a new approach for development going forward. An Openfire 3.10 branch has been created and the hope is that we will not have feature creep in this branch, but instead focus on stability and be able to make point releases when the situation warrants. In the past, Openfire's point releases (ie 3.9.0 to 3.9.1) was a mixture of bug fixes and new features. The new features will appear in other branches with an eye toward a future 3.11 or 4.0 release! We are always looking for more folks to help develop Openfire, so please send us those pull requests and stop by our XMPP MUC room email@example.com to say hi.
So please test this RC and report issues you find in the Openfire Support Forum. Do not report issues by commenting on this blog post please!
Here is a listing of download links and md5sums for this release. You can find these also on our beta download page.
The Ignite Realtime community is very happy and proud to announce the release of Smack 4.1.0, our open source XMPP client library. Since Smack 4.1 is not binary compatible with Smack 4.0, i.e. it is not a drop-in replacement, make sure to have a look at the "Smack 4.1 Readme and Upgrade Guide".
Smack 4.1 marks a milestone in the development history of Smack, as its obsoletes aSmack, the build environment formerly required to port Smack to Android. Starting with 4.1, Smack is able to run natively and unmodified on Android.
A further release highlight, among many others, is the support for XEP-198: Stream Management. Note that like every new big feature, Stream Management is disabled by default.
The full changelog can be found at https://www.igniterealtime.org/builds/smack/docs/4.1.0/changelog.html, the javadoc is available accessible via https://www.igniterealtime.org/builds/smack/docs/4.1.0/javadoc/ and the documentation available at https://www.igniterealtime.org/builds/smack/docs/4.1.0/documentation/
We would like to thank everyone who provided feedback, bug reports and contributed. The developers and contributors for the 4.1.0 release, since 4.0.0 are:
$ git shortlog -sn 4.0.0..4.1.0
631 Florian Schmaus
4 Vyacheslav Blinov
3 Anno van Vliet
3 Daniele Ricci
2 Georg Lukas
2 Júlio Cesar Bueno Cotta
1 Abmar Barros
1 Chris Deering
1 Christoph Fiehe
1 Gilles Cornu
1 Gligor Selimovic
1 Jae Jang
1 Luke GB
The signed tag used to upload the 4.1.0 artifacts to Maven Central points to 4bb8aea2815ceaab4224d1e2c3d80ba70c1f3803. As always, Smack 4.1.0 is available via Maven Central.
Now go ahead and implement a open source XMPP client with Smack. Be it for Android or one of the many platforms supported by Java. But even more importantly, provide feedback and help to improve Smack. We try our best to make Smack one of the best, stable and reliable open source libraries for XMPP, but it's far from being perfect. Join #smack (freenode) and discuss with us how Smack could be improved.