Community
Participate
Working Groups
In the Remote Systems view, choose New > Connection, and select "Team" as the parent profile. The connection is created, but when trying to expand a subsystem node, no children are expanded. Thus the connection is not usable. I consider this a major issue since it is the only way of enabling team support for connections (due to bug 142710) and we want to solicit feedback on team support.
In the team profile, I believe no default filters are defined. That means in order to make the files subsystem functional, you have to create new filters. If you create a filter does it work at all for you?
Created attachment 45543 [details] team view showing profiles
Right now this is working as designed in that the team profile defines no filters in it's filter pools by default. If new filters are created in the team profile then those will appear for subsequent connections created under that profile. I'll attach a screen shot of how filters appear defined in the profiles.
Hm, I see. Is it possible to have default filters defined in the default Team profile? Without filters, the Files subsystem is not really working well. But perhaps that's just a matter of documentation.
*** Bug 167961 has been marked as a duplicate of this bug. ***
Personally, I think that the user experience of not having any filter at all is a very bad one. That's also shown by looking at duplicate bug 167961. There should at least be an "All" filter predefined for every subsystem in every profile, in order to allow users actually use the new connection. In case this is not desired, users can delete this filter later on.
I've added the "root" filter for non-default profiles in file subsystems and I've added the "all" filter for non-default profiles in process subsystems.
Verification FAILED during TM 2.0M5 Testing: WinXP SP1, Sun 1.4.2_13, Eclipse-SDK-3.3M5, RSE-SDK I20070219-1615: After initial start on a clean workspace, Created a new Windows-dstore connection to "localhost" in the "Team" Profile. When expanding the "Files" subsystem, no filters are there.
Turns out this is a windows-specific problem. I had made the fix for RemoteFileSubSystemConfiguration, but DStoreWindowsFileSubSystemConfiguration overrides the filter creation.
This is now fixed for local and dstore-windows.
Looks good. I see the following default filters for files: Local (on Windows) - Drives FTP Only - Root Linux (Dstore) - Root Linux (SSH) - Root Linux (FTP) - Root SSH Only - Root Unix (Dstore) - Root Unix (SSH) - Root Unix (FTP) - Root Windows (Dstore) - Drives Windows (FTP) - Drives I also see "All Processes" as the default filter for processes. Marking as verified.
Closing verified M5 bugs
[target cleanup] 2.0 M5 was the original target milestone for this bug
