Last revised Feb 26, 2010
TM 3.1.2 service release includes 4 bug fixes compared to TM 3.1.1.
TM 3.1.2 is 100% upward and backward compatible with TM 3.1. If you already have TM 3.1, you can "check for updates" using the Eclipse update manager to get it.
See the TM 3.1.2 Build Notes for details.
TM 3.1.1 service release includes more than 59 bug fixes compared to TM 3.1.
TM 3.1.1 is 100% upward and backward compatible with TM 3.1. If you already have TM 3.1, you can "check for updates" using the Eclipse update manager to get it.
See the TM 3.1.1 Build Notes for details.
224 unique bugs were addressed since TM 3.0, including 23 API change requests.
See this report for details on all bugs, and this list for new API introduced.
See the TM 3.1 New & Noteworthy for new features
See the TM 3.1 Project Plan for supported operating environments
See the TM 3.1 Known Issues and Workarounds Wiki for known problems.
Some amendments to API specifications are worth noticing, and may require changes in client code even though they are binary compatible. More information can be found in the associated bugzilla items:
DefaultFileServiceCodePageConverter#convertFileFromRemoteEncoding()can now throw a RuntimeException when a remote file cannot be transcoded to the requested encoding without data loss .
ISubSystem.initializeSubSystemcan now throw a
SystemMessageExceptionon error. As per the Java API compatibility guide, this is not strictly a change breaking binary compatibility, but it does break source compatibility. In other words, you'll need to update your sources when you recompile, though old compiled bundles will continue to run .