From 29da955c0655fa946bc31914e0c1bd5babc59969 Mon Sep 17 00:00:00 2001 From: David Dykstal Date: Fri, 14 Mar 2008 17:39:14 +0000 Subject: [PATCH] [202630][api][persistence] SystemProfileManager.getDefaultPrivateSystemProfile() is inconsistent with ensureDefaultPrivateProfile() https://bugs.eclipse.org/bugs/show_bug.cgi?id=202630 --- .../concepts/cprofile.html | 15 +- .../rse/core/model/ISystemProfile.java | 4 +- .../rse/core/model/ISystemProfileManager.java | 6 +- .../rse/core/model/ISystemRegistry.java | 6 +- .../internal/core/model/SystemProfile.java | 51 ++- .../core/model/SystemProfileManager.java | 40 +-- .../internal/core/model/SystemRegistry.java | 201 ++++------- .../SystemTeamViewActiveProfileAction.java | 89 ----- ...SystemTeamViewMakeActiveProfileAction.java | 73 ++-- ...stemTeamViewMakeInActiveProfileAction.java | 75 ++-- .../ui/view/team/SystemTeamViewPart.java | 39 +-- .../team/SystemTeamViewProfileAdapter.java | 329 ++++++++---------- 12 files changed, 383 insertions(+), 545 deletions(-) delete mode 100644 rse/plugins/org.eclipse.rse.ui/UI/org/eclipse/rse/internal/ui/view/team/SystemTeamViewActiveProfileAction.java diff --git a/rse/doc/org.eclipse.rse.doc.user/concepts/cprofile.html b/rse/doc/org.eclipse.rse.doc.user/concepts/cprofile.html index ae5f934b342..fc38a14b115 100755 --- a/rse/doc/org.eclipse.rse.doc.user/concepts/cprofile.html +++ b/rse/doc/org.eclipse.rse.doc.user/concepts/cprofile.html @@ -3,7 +3,7 @@ - + Remote System Explorer Profiles @@ -13,30 +13,27 @@

Remote System Explorer Profiles

- When you define your first connection to your remote server, you will also define your first profile. All Remote System Explorer resources such as connections, filters, and filter pools are owned by a profile. Profiles help you manage these resources when you have a lot of connections. The Remote System Explorer creates a unique profile per team member (that person's private profile), plus a common profile called Team. The intent is to be able to share the Team profile in the future with other members of your team. You can also create your own profiles. + All Remote System Explorer resources such as connections, filters, and filter pools are owned by a profile. Profiles help you manage these resources when you have a lot of connections. The Remote System Explorer creates two profiles when starting up for the first time: a private profile, usually named after the host name of the machine that creates the workspace, and a profile called Team. The intent is to be able to share the Team profile in the future with other members of your team. You can also create your own profiles.

Profiles contain:
  • - Connections -- including subsystem properties. User IDs and passwords are not shared. + Connections -- including subsystem properties. User IDs and passwords are not shared.
  • Filters, filter pools, and filters pool references
  • - User-defined actions -
    • -
  • - Compile commands + Other artifacts associated with a profile

- Profiles can be active, or inactive. By default, only your private profile and the Team profile are active. The Remote System Explorer displays all connections from all active profiles and, within a connection, allows filter pools to be referenced from any active profile. Further, the user actions and compile commands shown in the right-click menu for a remote resource are from all active profiles. + Profiles can be active or inactive. The Remote System Explorer displays all connections from all active profiles and, within a connection, allows filter pools to be referenced from any active profile. Further, the user actions and compile commands shown in the right-click menu for a remote resource are from all active profiles.

- Your first profile will be for your local workstation. When you complete the steps for your first connection, you can decide whether to use your personal profile or the Team profile so that in the future you can share resources and information with other people. + Your private profile cannot be deleted or made inactive.