Skip navigation

Ignite Realtime Blog

7 Posts tagged with the beta tag
17

Spark 2.7.0 beta 1

Posted by Walter Ebeling Dec 23, 2011

Dear Community,

 

after some more weeks of testing, debugging and developing, we would like to ask for your support and publish the first beta of Spark 2.7.0. Ultimately, we would like to move Spark to Java 7, but that is currently not implemented via the installers. This will change in January after an update to the lastest version von Install4j provided by ej-Technologies.

 

You can find the nightly build for Windows here:  http://bamboo.igniterealtime.org/browse/SPARK-INSTALL4J-543/artifact/JOB1/Instal l4j

 

About Java 7: Spark 2.7.0 will run with Java 7. Please interchange the bundled JRE (located at Spark-install-folder\JRE) against a Java 7 JRE or use the installer named spark_2_6_3_12555_online.exe and install Java 7 as default on Windows. Using Java 7 will stop Spark from stealing the focus, when a new message is received.

 

Important Note: Oracle has introduced a bug in Java 1.6.0 u 25-27 that prevents Spark from closing automatically during the log-off on the Windows plattform. This is not Spark related. This affects all users that install the Spark version without an included JRE.

 

About file transfer: Spark 2.7.0 beta 1 is fixing an big bug with file transfer. Spark 2.6.x has an programmatic error that was making IBB file transfer very unstable. Tim Jentz deserves a big credit for finding this after weeks of debugging. Great job Tim!!!

Spark 2.7.0 will also move to a standard implementation for IBB file transfer. As a result of moving to the standard IBB implementation, you may have issues with transfer between Spark 2.7.0 and Spark 2.5.8 on IBB. This is an unavoidable result of obeying the standard. IBB is the fall back implementation, if Bytestream is not an option. Hence IBB is not the regular transfer method as it is much slower than Bytestream.

 

About plugins: There were large scale changes in the way Spark is dealing internally with plugins/extensions. All Plugin developers are kindly ask to review, if their plugins are still working. This applies also to Fastpath. Feedback regarding issues with this are highly appreciated.

 

About GUI: The Spark developers are only supporting JTattoo Luna. There are several reports that other skins are not working properly. This applies especially to Substance. If you are experiencing any GUI bug, please check if JTattoo Luna is also having this issue and report it.

As a general statement, I would urge all professional users to use the customizing options of Spark to get rid of Substance in corporate environments. The dev team may ultimately decide to remove Substance for 2.7x in a future release.

 

About Mac and Windows7 64 bit: The next Mac release is NOT secured. We are looking for a developer who can provide a Mac beta release. The integration to Windows7 64 bit is ok, but the flashing notification in the tray may or may not work. A tester and developer (MS C++ Code)  for this is also needed.

 

The change log for this beta is:

 

SPARK-1465     Checkboxes appear bigger then normal since the jtattoo update

SPARK-1464     When user accepts group chat invitation, status is always online

SPARK-1460     No group context menu on a right click

SPARK-1459     Update to the latest JTattoo version (Nov 2011)

SPARK-1452     If conferences tab is hidden, then Fastpath tab is hidden also

SPARK-1451     Vcard popup is not always showing up on mouse hover

SPARK-1450     When network connection is lost, chat window cannot be closed

SPARK-1449     UNC Path does not link to folder

SPARK-1445     Selecting 'Start a chat' in a group chat room opens an incomplete chat window

SPARK-1444     Subscription dialog shows the id value instead of the nickname

SPARK-1443     Privacy plugins cannot be accessed if we log into Spark through the IP address of the server

SPARK-1465     Checkboxes appear bigger then normal since the jtattoo update

SPARK-1464     When user accepts group chat invitation, status is always online

SPARK-1460     No group context menu on a right click

SPARK-1459     Update to the latest JTattoo version (Nov 2011)

SPARK-1452     If conferences tab is hidden, then Fastpath tab is hidden also

SPARK-1451     Vcard popup is not always showing up on mouse hover

SPARK-1450     When network connection is lost, chat window cannot be closed

SPARK-1449     UNC Path does not link to folder

SPARK-1445     Selecting 'Start a chat' in a group chat room opens an incomplete chat window

SPARK-1444     Subscription dialog shows the id value instead of the nickname

SPARK-1443     Privacy plugins cannot be accessed if we log into Spark through the IP address of the server

SPARK-1442     JabberVersion.java uses hardcoded value "Spark IM Client" for version name

SPARK-1441     ContactItem in shared group - right click popup menu performs copy when move is selected

SPARK-1440     Bug in ConferenceUtils.java that can break smack communication

SPARK-1439     Plugins are loaded in random order - plugins with no dependency has to be loaded first

SPARK-1438     Avatars are not scaled in user login/logout notification dialog

SPARK-1437     Bug in PrivacyManager that can break smack communication

SPARK-1429     Update French translation

SPARK-1427     Default Appearance/Colors cannot be overwritten through plugin;Group-Chat colors are hard-coded

SPARK-1423     typo error in LayoutSettings.java

SPARK-1422     persist vcard may throw file not found exception when jid is empty

SPARK-1421     Application version and application name are hardcoded

SPARK-1420     The messages in the set status message window is not getting deleted

SPARK-1419     Chat room configuration shows wrong roles for which presence is broadcast

SPARK-1418     Update simplified Chinese translation

SPARK-1414     Chat window is not flashing when receiving new message on Windows 7 64 bit

SPARK-1413     Update build.xml to check for Java 7

SPARK-1411     Sometimes file transfer indication is not updated on the receiving side

SPARK-1408     Remove "#" character next to Accounts button on the login screen

SPARK-1405     Improved last activity recognition

SPARK-1403     Enhance ability to extend core classes like ContactItem, ContactGroup, etc through plugin

SPARK-1400     Update to latest version Exe4J

SPARK-1381     Group Chat - Actions/Start a conference menu: propose bookmarked room (if any) instead of adhoc (random) room name

SPARK-1379     Support for XEP-0147

SPARK-1326     Make tabs position optional: TOP or BOTTOM; make search input appearance optional

SPARK-1324     SparkToaster showing avatars in real size

SPARK-1313     Enhance ability to overwrite spark properties values through plugin

SPARK-1215     Log out doesn't log out, it shuts down spark

SPARK-891       Typing notifications would be easier to see if also displayed near typing area

 

The beta release also includes a new Smack library that is based on Smack 3.2.1 plus the following bugfixes:

 

SMACK-362      smack throw NoSuchElementException if the muc#roominfo_subject has no values

SMACK-354      Provide milliseconds in timestamp colum debugwindow

SMACK-353      Thread leak in the FaultTolerantNegotiator

SMACK-350      Bytestream is not working in Spark 2.6.3 from XP to W7

SMACK-349      Smack's IBB sends too much data in a packet

SMACK-348      Documentation error - broken link

SMACK-346      Bug in return code for rejection handling in FileTransferManager

SMACK-343      Make Smack jar an OSGi bundle.

SMACK-338      IBB filetransfer doesn't work as expected

SMACK-336      There is an empty element in a SASL response

SMACK-335      Need to set file size and name for outgoing file transfer from input stream

SMACK-324      Investigate SASL issue with jabberd2 servers

SMACK-322      NPE in XMPPConnection

SMACK-263      Set file info in all send* methods

 

Expect a second beta in the first quarter 2012 that will include the latest final release of Smack

 

Please report issues in the Developer Forum

39

Hi

 

again an experimental Smack to fix IBB transfers for Spark 2.6.3. This is an experimental build with patches based on the Smack 3.2. branch. The patch itself is published in SMACK-351

 

The Smack code is not using IQ Stanzas for IBB file transfer since the implementation is not correct.  Smack 3.2.1 also breaks file transfers via IBB to Spark 2.5.8. This alpha should fix:

 

SMACK-350                    Bytestream is not working in Spark 2.6.3 from XP to W7

SMACK-349                    Smack's IBB sends too much data in a packet

SMACK-263                    Set file info in all send* methods

SMACK-335                    Need to set file size and name for outgoing file transfer from input stream

 

 

Copy into the lib folder of the Spark installation folder and report results.


Walter

 

P.S. Also fixes SASL against jabberd2 since http://issues.igniterealtime.org/browse/ SMACK-324 is included.

2

Spark 2.6 RC2 Released

Posted by Daryl Herzmann Apr 4, 2011

The IgniteRealtime community would like to announce the second release candidate of Spark before the final 2.6.0 release.  Much more detail on this release and files for download can be found here:

 

http://community.igniterealtime.org/docs/DOC-2157

 

We will continue to work on Spark 2.6.0 for the next 4 weeks. The release date for 2.6.0 is tentatively set to April 30th, 2011.  Please test and provide feedback!

4

on behalf of Robin Collier

 

Smack  3.2.0 Beta has been released on February 3, 2011.  It has been well  over 2 years since the last release, but much work has been done to fix bugs and add new features.  There are still other issues to be worked on, as there will always be, but it is time to start a new roadmap for Smack.

 

The  starting point will be this release with the intent to produce a more  regular release cycle.  I will try to outline a roadmap for future  releases in the near future based on the current set of issues, feedback  within the forums and of course developer contributions.

 

You can download from the Beta Releases downloads page.

13

Good things come to those who wait!

 

The Ignite Realtime Community is pleased to announce the beta for the next release of Openfire. This release contains a number of important  fixes and improvements to stability and XMPP protocol compliance. You can find a full list of fixed issues here. This beta is also the first version of Openfire to be released by the Ignite Realtime community under the Apache License v2.0.

 

You can download the 3.7.0 beta release here. Please provide us your feedback on the Ignite Realtime support forums. It would be helpful if you would tag your comments, discussions and questions with a tag that reads "openfire370beta"

 

As always, but particularly since this is a beta release, make sure to backup any existing version of Openfire and the persistent storage that it uses, before upgrading!

 

Some important security related notes to this release:

  • Openfire no longer ignores the system property to disallow password changes via XMPP. With previous releases, it was not possible to prevent users from changing their password via their XMPP connection. (CVE-2009-1596)
  • Fixed a XSS attack on the admin console login form.

 

Protocol compliance improvements:

  • Publish Subscribe (PubSub)
  • BOSH (http-bind) xml namespace compliance fix.

 

Some highlights of this beta release:

  • Improves how Openfire handles "idle" connections. Some of you may have  the system property xmpp.client.idle set to -1 to work around  previously broken behaviour. You may now let it default to 6 minutes or  set it to your preference.
  • Improved Openfire's caching to be less prone to memory exhaustion by correctly calculating cache size usage.
  • Fixed a bug where admin console login into a newly installed Openfire server would fail until restarted.
  • Fixed a bug with shared rosters within a LDAP environment.
  • Openfire now ships with the latest JRE (1.6.0u21).
  • A memory leak with the Personal Eventing Protocol (PEP) was fixed.
  • Openfire's custom log interface has been replaced with SLF4J and a Log4J backend.
  • Fix issues with self signed SSL certificates.
  • A number of improvements and fixes were made to the Multi-User Chat (MUC) configuration pages on the admin console
  • There were also some improvements made to the plugins.
  • There are also French, Russian, and Lithuanian langauge translation fixes for Openfire and some of the plugins.
9

XIFF 3 Beta

Posted by David Smith Apr 2, 2008

I'm happy to announce that we've just released an initial beta of XIFF 3.0, our open source ActionScript library for building XMPP clients. Continuing along the path set by Sean and the previous developers of XIFF, we've moved to embrace ActionScript 3 and Flex, while adding significant functionality improvements at the same time. Highlights include BOSH support, VCard support, and redesigned APIs. Feedback is strongly requested; It has been quite a while since a XIFF release, and a lot of things have changed, so I will be interested to see how the community feels about the direction we've taken things.

 

Some parts of this new release are still in a transitional stage. For example, SASL support is only available for BOSH connections at the moment. As more code is generalized between the BOSH and Socket connections, this limitation will go away.

4

During the last few years we have been listening to the community and our Openfire Enterprise customers. You all had the same question: "When will Openfire support clustering"?

 

I'm happy to report that Openfire 3.4.0 Beta now has support for clustering. Clustering will let you run several machines serving the same domain thus allowing you to scale your services and at the same time providing continuous service even if one machine goes down. Today we are officially starting the beta process that will last until October 31st.

 

Unlike other Ignite beta programs, this beta comes with benefits and important discounts for those of you that help us test the server. We had to rewrite big portions of the server, and we would like to get many people testing the server to ensure a better product. We thought these incentives might help us recruit more beta testers.

 

You should know that we have initially tested the server internally and even deployed it to our public servers, so this beta may be more stable than some other beta products.

 

People interested in participating in the beta program can read this welcome document to learn more about the benefits and discounts you can get by participating.  You can find all of the information (download links, documentation, instructions, and more) in the new Openfire 3.4.0 Beta space in the Ignite Community.