From 3895ee76059aa48e402c3bfa3ec370c1815a23e1 Mon Sep 17 00:00:00 2001 From: Martin Oberhuber < martin.oberhuber@windriver.com> Date: Thu, 22 Feb 2007 22:28:21 +0000 Subject: [PATCH] [cleanup] fix copyright year 2007 --- .../guide/Artifacts.html | 2 +- .../guide/Communications.html | 2 +- .../guide/DataElements.html | 2 +- rse/doc/org.eclipse.rse.doc.user/notices.html | 2 +- .../tasks/tteamsup.html | 274 +++++++++--------- 5 files changed, 141 insertions(+), 141 deletions(-) diff --git a/rse/doc/org.eclipse.dstore.doc.isv/guide/Artifacts.html b/rse/doc/org.eclipse.dstore.doc.isv/guide/Artifacts.html index a45c4741edb..e2212a9bade 100755 --- a/rse/doc/org.eclipse.dstore.doc.isv/guide/Artifacts.html +++ b/rse/doc/org.eclipse.dstore.doc.isv/guide/Artifacts.html @@ -3,7 +3,7 @@ - + RSE Artifacts diff --git a/rse/doc/org.eclipse.dstore.doc.isv/guide/Communications.html b/rse/doc/org.eclipse.dstore.doc.isv/guide/Communications.html index 3446f6fd8ec..957c6928917 100755 --- a/rse/doc/org.eclipse.dstore.doc.isv/guide/Communications.html +++ b/rse/doc/org.eclipse.dstore.doc.isv/guide/Communications.html @@ -3,7 +3,7 @@ - + RSE Model diff --git a/rse/doc/org.eclipse.dstore.doc.isv/guide/DataElements.html b/rse/doc/org.eclipse.dstore.doc.isv/guide/DataElements.html index 59745c901e5..b82f963e624 100755 --- a/rse/doc/org.eclipse.dstore.doc.isv/guide/DataElements.html +++ b/rse/doc/org.eclipse.dstore.doc.isv/guide/DataElements.html @@ -3,7 +3,7 @@ - + RSE Model diff --git a/rse/doc/org.eclipse.rse.doc.user/notices.html b/rse/doc/org.eclipse.rse.doc.user/notices.html index 1f694c82f5a..2b7a4b4dc05 100755 --- a/rse/doc/org.eclipse.rse.doc.user/notices.html +++ b/rse/doc/org.eclipse.rse.doc.user/notices.html @@ -2,7 +2,7 @@ - + diff --git a/rse/doc/org.eclipse.rse.doc.user/tasks/tteamsup.html b/rse/doc/org.eclipse.rse.doc.user/tasks/tteamsup.html index 88fb6da8b80..1899cb2a557 100755 --- a/rse/doc/org.eclipse.rse.doc.user/tasks/tteamsup.html +++ b/rse/doc/org.eclipse.rse.doc.user/tasks/tteamsup.html @@ -1,137 +1,137 @@ - - - - - - - - -Using team support - - - - -

Using team support

-
-
You can use any Eclipse-enabled repository from any -vendor. The following -information describes project-sharing using Concurrent Versions System -(CVS) support that comes with Eclipse. Steps and user interface -elements will differ depending on the repository -support that you have installed. -
Note: When you -synchronize your RemoteSystemsConnection project with the repository -the first time, you will see many files in conflict. -This is because it takes one synchronization to properly align -the server's encoded version information with your local files. This -happens only once and you can just receive all of the incoming changes -and your local workspace will then be synchronized with the server. You -might also find inactive profiles that belong to other teammates in the Team -view after you synchronize with the central server. You can choose whether -or not to activate these profiles in the Team view if you want to see the -profile's contents in the Remote System Explorer on your local workstation.
-

In a team programming environment, team members do work in their own workbench, -isolated from others. Eventually they will want to share their work with -their teammates. The Remote System Explorer allows them to share -their connections, filter pools, and filters. To share these resources:

-
-
    -
  1. In the Remote System Explorer perspective, select the Team tab which by - default is located in the same pane as the Remote Systems view. This - will bring the Team view to the front of the Remote System Explorer. - You can also use themenu -button on the Remote Systems view and select the Work -With Profiles action.
    2. -
  2. Expand RemoteSystemsConnections. The profiles that you have defined, as well as the Team profile, are displayed. The Team profile is created by the Remote System Explorer to use for sharing connections, filter pools, and filters if you do not want to share them in a profile that you create and manage.
    3. -
  3. Right-click on RemoteSystemsConnections -and select Team > Share Project .
    4. -
  4. Select CVS and click Next.
    5. -
  5. Select Use existing repository -location if you have already defined a CVS repository. Select Create a new -repository location if you need to define a CVS repository (this -information should be available from the person who configured the CVS -repository on the server). To create a CVS repository definition: -
      -
    1. In the Host field, type the -address of the server, for example mymachine.com.
      2. -
    2. In the Repository path field, -type the path to the repository on the server, for example /home/test, d:/test.
      3. -
    3. In the User field, type the -user name to use to connect to the repository.
      4. -
    4. In the Password field, type -the password for the user name.
      5. -
    5. From the Connection Type -list, select the authentication protocol of the CVS server. There are three -connection methods that come with the Eclipse CVS client: -
        -
      • pserver: A CVS specific connection method.
        • -
      • extssh : An SSH 1.0 client included with the workbench.
        • -
      • ext: The CVS ext connection method that uses an -external tool such as SSH to connect to the repository. The tool used -by ext is configured in theTeam > CVS > EXT -Connection Method preference page.
        • -
      -
      6. -
    6. If the server uses a custom port, -enable Use Port and -enter the port number.
      7. -
    -
    6. -
  6. Click Finish. The repository -location is -created. The RemoteSystemsConnections project will be created remotely and the Synchronize view will open and - allow you to commit its resources to the server. If the project already - exists remotely, the Synchronize view will show conflicts on any files - that exist both locally and remotely. If the RemoteSystemsConnections project -already exists in the repository when you first share it, there may be -many conflicts. Generally, these are not real conflicts, but simply considered -conflicts on the first synchronize because there is no local CVS information for the -resources in your workspace. -If you have not created any resources in your Team profile, you can -safely send or receive all of the conflicting files. If you have created -resources in your Team profile, you should check each conflicting file to ensure -there really are no differences, and if there are, resolve them by merging.
    7. -
  7. To synchronize your resources with those -in the associated repository, right-click on the RemoteSystemsConnection - project, and select Team > Synchronize -with Repository.
    8. -
  8. After sharing or synchronizing, and -receiving incoming resources from the repository, right-click on the RemoteSystemsConnection project, -and select Reload Remote System Explorer. This refreshes -the Remote System Explorer and Team view to reflect the new or changed -resources.
    9. -
-
-
-

Viewing the project resources in the Navigator -view

-
-
The Navigator view provides a hierarchical view of all -the resources in the workspace. From here, you can view the contents of the projects -that are shared, including the RemoteSystemsConnection -project, and select team-related actions on particular -resources. By default, the Navigator view is included in the Resources perspective. -To add it to the current perspective, -
    -
  1. Select Window > Show View > Other.
    2. -
  2. Expand Basic.
    3. -
  3. Select Navigator.
    4. -
-
-
-
-
-

Related concepts
-Team support
-Remote System Explorer -Profiles
-

-

Related tasks
-Working with profiles and team support
-

-
-
- - + + + + + + + + +Using team support + + + + +

Using team support

+
+
You can use any Eclipse-enabled repository from any +vendor. The following +information describes project-sharing using Concurrent Versions System +(CVS) support that comes with Eclipse. Steps and user interface +elements will differ depending on the repository +support that you have installed. +
Note: When you +synchronize your RemoteSystemsConnection project with the repository +the first time, you will see many files in conflict. +This is because it takes one synchronization to properly align +the server's encoded version information with your local files. This +happens only once and you can just receive all of the incoming changes +and your local workspace will then be synchronized with the server. You +might also find inactive profiles that belong to other teammates in the Team +view after you synchronize with the central server. You can choose whether +or not to activate these profiles in the Team view if you want to see the +profile's contents in the Remote System Explorer on your local workstation.
+

In a team programming environment, team members do work in their own workbench, +isolated from others. Eventually they will want to share their work with +their teammates. The Remote System Explorer allows them to share +their connections, filter pools, and filters. To share these resources:

+
+
    +
  1. In the Remote System Explorer perspective, select the Team tab which by + default is located in the same pane as the Remote Systems view. This + will bring the Team view to the front of the Remote System Explorer. + You can also use the menu +button on the Remote Systems view and select the Work +With Profiles action.
    2. +
  2. Expand RemoteSystemsConnections. The profiles that you have defined, as well as the Team profile, are displayed. The Team profile is created by the Remote System Explorer to use for sharing connections, filter pools, and filters if you do not want to share them in a profile that you create and manage.
    3. +
  3. Right-click on RemoteSystemsConnections +and select Team > Share Project .
    4. +
  4. Select CVS and click Next.
    5. +
  5. Select Use existing repository +location if you have already defined a CVS repository. Select Create a new +repository location if you need to define a CVS repository (this +information should be available from the person who configured the CVS +repository on the server). To create a CVS repository definition: +
      +
    1. In the Host field, type the +address of the server, for example mymachine.com.
      2. +
    2. In the Repository path field, +type the path to the repository on the server, for example /home/test, d:/test.
      3. +
    3. In the User field, type the +user name to use to connect to the repository.
      4. +
    4. In the Password field, type +the password for the user name.
      5. +
    5. From the Connection Type +list, select the authentication protocol of the CVS server. There are three +connection methods that come with the Eclipse CVS client: +
        +
      • pserver: A CVS specific connection method.
        • +
      • extssh : An SSH 1.0 client included with the workbench.
        • +
      • ext: The CVS ext connection method that uses an +external tool such as SSH to connect to the repository. The tool used +by ext is configured in theTeam > CVS > EXT +Connection Method preference page.
        • +
      +
      6. +
    6. If the server uses a custom port, +enable Use Port and +enter the port number.
      7. +
    +
    6. +
  6. Click Finish. The repository +location is +created. The RemoteSystemsConnections project will be created remotely and the Synchronize view will open and + allow you to commit its resources to the server. If the project already + exists remotely, the Synchronize view will show conflicts on any files + that exist both locally and remotely. If the RemoteSystemsConnections project +already exists in the repository when you first share it, there may be +many conflicts. Generally, these are not real conflicts, but simply considered +conflicts on the first synchronize because there is no local CVS information for the +resources in your workspace. +If you have not created any resources in your Team profile, you can +safely send or receive all of the conflicting files. If you have created +resources in your Team profile, you should check each conflicting file to ensure +there really are no differences, and if there are, resolve them by merging.
    7. +
  7. To synchronize your resources with those +in the associated repository, right-click on the RemoteSystemsConnection + project, and select Team > Synchronize +with Repository.
    8. +
  8. After sharing or synchronizing, and +receiving incoming resources from the repository, right-click on the RemoteSystemsConnection project, +and select Reload Remote System Explorer. This refreshes +the Remote System Explorer and Team view to reflect the new or changed +resources.
    9. +
+
+
+

Viewing the project resources in the Navigator +view

+
+
The Navigator view provides a hierarchical view of all +the resources in the workspace. From here, you can view the contents of the projects +that are shared, including the RemoteSystemsConnection +project, and select team-related actions on particular +resources. By default, the Navigator view is included in the Resources perspective. +To add it to the current perspective, +
    +
  1. Select Window > Show View > Other.
    2. +
  2. Expand Basic.
    3. +
  3. Select Navigator.
    4. +
+
+
+
+
+

Related concepts
+Team support
+Remote System Explorer +Profiles
+

+

Related tasks
+Working with profiles and team support
+

+
+
+ +