Community
Participate
Working Groups
Currently, there are several places in RSE code where the systemType is explicitly queried. For instance, in CommandsViewPage line 374: if(...cmdSubSystem.getHost().getSystemType().equals("Windows")) EnvironmentVariablesPromptDialog line 114: if (systemType.equals("Windows")) There are many more places where the systemType is explicitly used to make some decisions (just search for String "Windows"). Code like this is problematic when the list of available services is discovered automatically, so it is not possible to specify a particular systemType. Instead of querying the systemType, code should rather query existence of particular properties in IHost -- e.G. IHost.getProperty("OSType").startsWith("win") This would also make it possible to get rid of special code for the Local subsystem, that's using a different method of finding out whether it is running on Windows than the other subsystems -- it would just have a fitting property.
Promoting to Plan Item. More desired features include * Properties of SystemType being specified like - isCaseSensitive etc. rather than explicit check for the name of the system type * Services being grouped into a system (bug 150265) * More dynamic enabling / disabling of subsystems / services based on availability * Allow Services (like a Registry) to be first-class objects, or hook them below Local? * Each SystemType to have a primary means of connection (defined by the wizard), plus additional registered optional services * Group system connections to logical units (multi-core / multi-system)
Important work on this has been completed: bug #186640 (properties on IRSESystemType) bug #150265 (createHost() with subsystem IDs) bug #173468 (adding standard service name to the subsystem) bug #159522 (adding shell processes as a service dependent on other services) For the future, more work will be needed especially to address bug #176490, an improved UI for assembling connections created out of services with more flexibility.
[target cleanup] 2.0 M7 was the original target milestone for this bug
