Date: June 22, 2014
From: Bob Jacobsen
Subject: Test version 3.7.8 of JMRI/DecoderPro is available for download.
Note that this release is intended to be final patches before the release of production JMRI 3.8. We'd very much appreciate your feedback on it.
This is a test release. Please post a note if you encounter any new or old bugs! And please back up your JMRI files before installing this, in case you want to go back to an earlier version.
This is the next (hopefully last) in a series of test versions. We expect this series to end in a JMRI 3.8 production release around the middle of 2014.
Some of the changes involved are quite extensive. They may require a certain amount of experience before they are working well. Therefore, this test version should be considered experimental.
JMRI is now only available under the GNU General Public License. For more information, please see our copyright and licensing page.
The decoder definition files have been reformatted to make them easier to maintain. If you want to make a change in a decoder definition file, please start with a file from JMRI 3.7.6 or later.
The XmlIO web service has been deprecated and is scheduled to be removed in JMRI 3.11 (July 2015). All users who are relying on direct access to the XmlIO API are recommended to begin using the JSON API. inControl web throttle users are recommended to begin using webThrottle instead, or to plan on investing in devices that can support webThrottle, the iOS WiThrottle, or the Android Engine Driver.
This release series has some changes to the application-initialization structure, particularly in the apps.Apps class. If you have written code of your own that runs applications based on JMRI, please check for use of deprecated methods.
The internals for handling CV read and write addressing have been extensively reworked. The change should be transparent (invisible) to users. If you do notice anything problems involving CV reading, writing, storage or anything else, please let us know.
The configuration structure for JMRI is changing to use Configuration Profiles. Configuration Profiles allow a single JMRI application to have multiple, user selectable, configurations that can be changed as application startup. For some users, this change will have no impact; other users will be visibly impacted by this change. See http://jmri.org/help/en/html/profiles.shtml for more information.
The JMRI SRCP implementation is undergoing extensive revision, in part due to testing with 3rd party SRCP clients and servers. If you are using the SRCP support, you will need to upgrade both the client(s) and the server to the same JMRI version.
The JMRI Web Server is being extensively rewritten. If you notice any problems using it, please let us know.
This release, and all other releases in this cycle, require Java 1.6 or newer.
None at the time of this release.
Please use these links for downloading:
Put the creation of each block xml element into a try/catch. There is an issue where the block data isn't being saved but at this stage I have no idea what the trigger is and have had no log files from a user to help narrow it down or replicate it. Doing this will at least prevent all block data from being lost during a save. (r26333)
Ensure that the file paths are correctly loaded from the configuration file, and that the user files (preferences:) path is loaded before other paths. Ensure that the scripts path ends with a file separator character.(r26344)
Support for the RR-CirKits MotorMan (r26387)
Daniel Boudreau made the following changes to Operations: