Release Notes
The Rio team would like to announce the release of Rio 4.2.
Rio 4.2 is download
4.2 Release Notes
The full list of changes can be found in our issue management system, and is reproduced below.
Bug
- RIO-267 - CLI does not display monitor attributes when invoked in non-interactive mode
- RIO-297 - Obtaining pid for forked service
- RIO-298 - Rio 4.1 Release is not compiled with gnostic
- RIO-299 - Typo in EventConfig.groovy in the Event Example
- RIO-300 - If a forked service detects that its parent cybernode has gone away, the service's preDestoy method is not called
- RIO-301 - EventHandler not set correctly for SLA
- RIO-302 - Dependency type of pom causes createJar to fail
- RIO-303 - Rio test manager deletes log files from previous test
- RIO-304 - If repository declaration in pom spans lines the parsed repository contains illegal characters
- RIO-305 - Allow support to be able to resolve artifacts from a local repository that is served up
- RIO-306 - When changing groups to ALL_GROUPS (or ALL, all, or all_groups) using the CLI, the group is not set correctly
- RIO-308 - RioTestRunner test configuration does not accept a maven artifact id for its opstring
- RIO-309 - Pom properties used in dependency version numbers are not resolved at deploy time
- RIO-310 - Failed forked services are not destroyed when the OpString is undeployed.
New Feature
- RIO-271 - Add Cybernode enlist/release semantics to CLI
- RIO-296 - Limit port range for exporters and Webster
Release notes for previous versions
