Subeclipse Getting Started Guide

 

Subeclipse getting started learning guide (from http://jdonee.javaeye.com)

Preface

I encountered many problems when using subclipse. After searching for Google, I found that there was no detailed explanation of the subclipse plug-in on the Internet, and some provided simple installation and use tutorials, or some English tutorials will help us who don't want to read e, so I decided to put subclipse's documents in Chinese, to help friends and colleagues who don't want to read the English documents. Of course, they have their own documents for future reference. I hope you can correct the errors and shortcomings.

 

The following is the version of the related software:

Tortoisesvn 1.5.2

Subversion 1.5.1

Subclipse1.4.3 and later (online installation address: http://subclipse.tigris.org/update_1.4.x)

Subversion client adapter 1.5.1 and later

Subversion native library adapter (javahl) 1.5.1.1 and later

Eclipse3.4

 

I,Getting startedThis section describes the basic operations of the svn plug-in, such...

• Create a version control repository
• Connect to a repository address
• Import new project to Warehouse
• Export a project from the repository to your workspace

II,Daily homeworkPart focuses on maintaining the daily work cycle:

• Edit
• Update
• Submit a job
• Synchronize repository (using synchronize view)

 III,ReferenceThis section describes each function of the plug-in detail.

 

 IV,FAQThis section provides quick answers to some common problems.

 

No matter how you are new or familiar with SVN, you can use this plug-in to operate SVN and then operate SVN Based on command lines, you may find that this is the best starting point for learning and using SVN.

Getting started

• Create a storage location
• Import a new project to the repository
• Connect to a project with SVN
• Check out items

Overview of creating a storage location

You must define the storage location in Eclipse IDE before using an SVN repository.

Procedure

GenerallySVN RepositoryCreate and use your repository address in the view. It belongsSVN repository restore ing perspective(SVN repository scan perspective. When you need to create a new repository address, clickAdd SVN RepositoryClick the button or right-click the perspective and choose new> repository location...

 

 

The add SVN repository dialog box displays the URL of your storage location. Enter the information you want to connect. No authentication information. Please define this location. It is required when SVN requests your user and password information.

InAdd SVN RepositoryThe dialog box prompts you to enter the URL of the storage location. Of course, the input repository address must be connectable. No authentication is required for defining the location. It is required only when SVN requests your user and password information. The main advantage of this method is that SVN is used to manage your password. When your password is changed, it will prompt you to enter a new password. It also caches and encrypts the new password.

 

When you click Finish, The Wizard will create the storage location. Expand it to view the content in the specified address.

 

 

 

Import a new project to the repository Overview

This is the process of importing a new project in your eclipse workspace to the repository so that you can manage it through SVN. If you have used SVN and you have copied existing projects in your workspace, you may need to referConnect to an existing project(In the following section.

Procedure

If you are not ready to import your project to the repository, create a simple project that contains some files so that they can be stored in the repository. You can achieve this simply by selecting File> New> project... and plug-in development> plug-in project, provide the project name, click to complete this wizard, and create a sample plug-in project.

To import a project to the repository, right-click the project to be imported, and select team> share project from the menu bar...

 

 

This will enable the share Project Wizard, select the repository type such as SVN, and click Next.

 

If you have defined a storage location to store the project, select it in the list and click Next. Otherwise, select the "Create a new repository location" option and click Next. If you want to create it, seeCreate a storage locationTo query more information.

 

 

You must specify a folder name for the stored project. The folder name is a relative URL stored in the previous step of the specified location. All intermediate folders must already exist in the repository, but the final folder name cannot. You can use the Browse... button to select a path from the repository. The Browse dialog box also allows you to create folders so that you can use this option to create any intermediate folders. In the above example, we will define the structure of "projectname/trunk" according to the Project Storage conventions. In this example, the projectname folder must already exist and the trunk folder must not. When you finish, click Next
Or finish.

When using browse..., make sure that the selected URL exists. Otherwise, the window will pop up continuously, which may cause program crash.

 

 

The last page of the Wizard is just a confirmation page. When you click Finish, SVN will call upMkdirCommand to create an empty folder at the specified location of the repository. The folder is checked out to your local project. This step will create the. svn folder inside the project, so that it becomes a validProject copy. Finally,Submit dialog box, Submit anything you can submit to the repository. Of course, you do not have to submit anything or anything else. You may also want to cancel the submit dialog box, return to your workspace, and perform other operations on the team menu. For example, if you want to set SVN attributes such as "commit ",
> Add to version control options, and then use the team> set property options. Once your stuff becomes the way you want it, you can execute team> commit.

 

Topic:. SVN is a set of hidden folders.

 

Overview of connecting a SVN Project

This is the process of connecting to SVN when an existing project is copied in your workspace. If you have a brand new project to import to your repository, please referImport a new project to the svn Repository.

Procedure

This process assumes that you already have an existing project in your workspace and the project is a valid working copy. Select the svn project you want to connect to, and right-click and select team> share project...

 

 

This will enable the share Project Wizard, select the repository type such as SVN, and click Next.

 

 

The Wizard will check whether the. SVN metadata folder is valid in the root directory of the project that you originally selected to share. If you find these folders, you will see screenshots as shown in. If you do not see this screenshot, And you are prompted that this is a new project screenshot, you should cancel this wizard. This means that the wizard does not acknowledge that this is an existing work copy. If you continue, the wizard willImport a new project to your RepositoryTo process it. Otherwise, if you see the preceding figure, click Finish to connect to the svn project. The Wizard will be completedSubmit dialog boxAnd submit any locally modified files. If you do not want to do anything at this time, you can cancel this dialog box.

 

Question: The SVN project here refers to the project you checked out using other SVN client tools.

Check out Project Overview

Check-out is a proprietary term. It refers to the process of generating a copy from a project in the repository and copying it to your local workspace. In SVN, a working copy is created during the check-out process. A working copy is a folder structure in a special format. It contains some extra. SVN folders, which store SVN information and retain an original copy for each item in the project after the project is checked out.

Process

BecauseCheck outDirectly corresponds to your repository, then navigateSVN repository restore ing perspective(SVN repository scanning perspective. If you have not defined a connection for your repository, you must first Add a new storage location.

 

 

Select the desired repository directory, and right-click the context menu and select checkout.

 

 

 

If the. project file of eclipse already exists in the selected repository folder, the check-out wizard automatically detects the method by default and uses the project definition file. If the. project file does not exist in the repository folder, the wizard allows you to check out the folder by using the standard Eclipse project or the new project wizard.

 

 

Next, you will be able to find the working copy you have created. The system creates a work copy in your eclispe workspace. To select another location, deselect the use default workspace Location Option and enter a new destination address or browse.

Subclipse task

Preface:

 

Content

• Edit, update, and submit code
• Use synchronization View
• Create and apply patches
• Maintenance Branch

Typical job cycle: Edit, update, and submit

 

SVN is the same as most other scms systems. Once you check out your project or share it with others, all you have to do is perform the following simple cycle:

1. Edit: Check out the project modification code from the server
2. Update: update the local file to the latest version on the server.
3. Submit: submit local modifications to the server

In eclipse, the svn plug-in combines the special functions of SVN with the eclipse team topic, making the maintenance cycle very easy.

 

ASIDE: the SCM here is not the supply chain relationship management that we understand, but the source code control management.

Edit work copy

When you edit a work copy, observe the records (such as files and folders) in the resource and you will findNavigatorSimilar to other views, a view is based on the same information, such as the Java Development toolbar (Java Development Tools)Package Explorer.

As long as you use eclipse to operate your work copy, eclipse will capture your changes and refactoring. You can compare the svn command line tool to perform renaming, deleting, and moving operations on your work copy. The SVN plug-in of eclipse can also meet these requirements.

There is a special case when adding resources: the new file or folder you created must be added to your work copy. On the new resource, right-click the context menu and choose "team">"Add to source control"Command. If you do not do this, the svn plug-in will display a question mark (?) next to the resource (?), That is to say, an unknown file appears in your working copy. However, once it is added, the resource will be marked with an asterisk. Finally, when you submit your changes, the tag will disappear. If you want to ignore the added resource, it will still appear inSubmit dialog boxBut is not selected by default.

If you want to exclusively access a file to be edited, you can lock (Lock.

Updated working copy when others submit changes

When you are coding, editing, debugging, and so on, other people (if you work in a team) may also change this project. To keep up with the progress, you must update them before each task, even if your changes are stable. You should also update them immediately before submitting your work. Every part of the updates you modified in the project resources will be followed, and SVN will try to merge these changes. This results in no overlap between your changes and those in the repository. However, if the changes conflict with each other, the affected resources in your work copy will be marked as conflicted, and some text tags will be released, which leads to the differences between the repository and your changes. You can manually correct these conflicts, or click"Edit
Conflicts"Command correction (they ). If you edit the text to resolve the change, you need to mark the resolution of the conflict.
The most challenging approach is to restore (Revert) Make your own changes and start again.

Submit changes to the repository

Once you are satisfied with the current change, submit now (Commit)They are stored in the repository. SVN will keep the changes you submitted in sync and force you to update every conflict, but only when the affected resources must be updated will they be overwritten. In any case, if the dependent resources (for example, the files you update are required for a program file) are updated, their original relationships will not be verified after submission. This is why you need to update and check your changes first.

 

Overview of using synchronization View

If you want to see the overall status of your working copy, including any updates, and compare it with the status of the repository, the synchronized view is very useful. This view focuses on changes to the inbound and outbound modes (Inbound) Changes refer to other submitted changes that will be made in the same step in your work copy. Outbound (Outbound) Changes focus on a series of results submitted to the repository, such as editing, deleting, or adding local resources.

In short, the synchronization view provides another perspective for you to update and submit your work. This will make you feel more appropriate as an eclipse user.

 

Overview of creating and applying patches

Generally, when a work project is shared among many developers, You need to review and possibly transfer changes when they are not submitted. To accelerate the development process, SVN provides the patch creation function, which works with the built-in functions of eclipse to apply patches.PatchIt is a statement of a specific version changed to the repository status and can be easily passed to other developers. For example, when a developer (who has no permission to submit) needs to submit a change, someone can review the changes and submit it.

Create patch

Select your project or folder/file, and right-click "team"> "create patch. Save the patches to a file and then distribute them by email or similar means.

You must use the "team"> "add to Version Control" option to include the new file in the patch before creating the patch. This tells SVN to include it in the patch.
 

Application Patches

Select your project or a folder or file, and right-click the "team"> "Apply patch..." option. It will guide you through the wizard, first let you specify the patch location, and then apply it to your project copy.

Maintain SVN branches

Like many other scms systems, SVN also has the concept of "working with different branches of the same project. That is to say, some parts of the repository are independent from each other based on different development baselines. However, configuration changes may work together, including changes between all branches and replication branches.

Generally, the "Main (main)" baseline developed in the project is called in SVNTrunk (trunk ),However, this is not a technical requirement, but an agreement.

The SVN library model is different from CVS (supporting the mechanism that the tag/version and branch are in the same path), and supports the branch and tag in the "product copy" mode. Because replication is relatively simple, and tracing for specific resources is more simplified. Generally, SVN repositories classify storage groups into three types:

• Trunk is also the main line of project development. Developers usually submit some changes to it on a regular basis.
• Tags (TAG)-a group of snapshots of the trunk (or branch) at a custom time point, such as the product release date.
• Branches (Branch)-it is an active variant compared to the main (or even other branches) in the project. This is useful when one (Major) change in development requires coordination within the team, or project changes in a single work copy are no longer feasible.

Although this Convention is roughly equivalent to how the CVS structure uses tags (versions) and branches, the method you choose depends entirely on you (and your team ), you should consider this when defining and setting a repository.

If you create a repository as recommended, you will be clearer and clearer when talking about the tag, branch, and merge.

Mark

If most of the work of a project has been completed in the "trunk" of the repository, you may need to "save status" in the repository ", for example, when you release a version for a product or milestone that follows. Of course, you can also just write down your current revision number, and then you can always use this information to recreate the project content, or compare it with it. However, you can also give a clear tag name for your convenience.

 

Comparison: In the svn command line, you only need to useSVN CPCopy the repository address (such as http: // svn-server/bigproj/trunk/) to a new and different address (suchHttp: // svn-server/bigproj/tags/client-release-0.99/).

 

By using the Eclipse plug-in, you can right-click "team" to find the "branch/Tag..." function.

As agreed, you cannot submit anything at the "tag" location of a repository, which only exists due to a specific repository revision. Even so, no operation will prevent your submission to the tag) "Location (although the create branch/Tag dialog box prompts you to warn when the URL contains the" tags "character ). Tags is just the svn convention. If you need to copy a copy to work in different directories, use a branch. In fact, submitting to a tag folder also has some benefits. Because you want to include these updates on the tag, including the version number and (or) Release Date files.

Branch

Creating a branch is the same as creating a tag. It is a copy of a basic repository. If you need to work in the branch immediately, use the same working copy (that is, your Eclipse project), right-click the 'team> Switch 'command to switch to the new location.

If you want to set a branch for this operation, clear the "Create a copy on the server" check box (as described in the command syntax: your local modifications will be applied to the basic version you want to copy ).

Select a branch or tag job

Creating a branch or tag does not change your working copy. Instead, you need to switch to the newly created repository address (or another sub-address ).

Note: you do not need to switch the entire project. You can even switch to any level of folder or a separate file. However, before a single submission, this will make the analysis changes more difficult to understand.

Merge changes

If a branch job depends on the branch maintenance personnel to regularly maintain changes on the trunk, these changes may be merged into the branch. To do this, you can use 'Team> merge', which can be applied to the comparison differences between the two different revisions on the trunk.

For example: Alice and Bob and Charlie, two other team members, work in the "X" project. Alice needs to make significant adjustments to the user interface, so she creates a branch named "gui_changes" on the trunk. This submission is based on revision 8. At that time, Alice switched to this position, left the project trunk and operated on her own as she expected. Later she submitted some changes in the branch. At the same time, Bob and Charlie have been working on the trunk, and the revision of the entire repository has reached 12 (remember that the revision counter is public, any changes will increase .)

To keep up with the development speed of the team, Alice needs to add the changes produced on the trunk to her branch. Select 'Team> merge... 'from the "team" menu to enter the correct URL of the project to be switched. If the dialog box displays http: // svn-server/SW-dev/branches/gui_changes/Project-x/, she will have to modify
Http: // svn-server/SW-dev/trunk/Project-x/, in"From"Enter '9' for revision, and then in"To"Amendment input" 12 (orHead) ", And then merge. This will allow her work copies to get the latest changes on the trunk, and she can submit them to the branch (once there is any conflict, you must first resolve the [conflict]).

Note: It is best to use a "clean" working copy when merging changes (that is, no changes). This is a good idea because you may submit differences (or just differences) and record the corresponding revisions. Some SCM systems can automatically monitor them (using "changes"), but SVN does not (although this feature will be put on the agenda in future versions ).

Apply changes in the branch

The application changes when recovering from a branch to the trunk, and vice versa. For details, see the merged document.

Backporting

Some branches are only used to maintain copies or release preparation, and then cleared. However, sometimes the changes submitted by the branch are very useful. You can put them in the project trunk. This process is called "backporting". application changes between the specified branch revision and trunk are also considered to be used in combination, simply reversing the inherent roles.

Reference (I) Content

• Repository exploration perspective
• Group Synchronization perspective
• View
• Group menu
• Control Menu
• Alternative menu
• Other actions
• SVN protocol support

Overview of SVN repository exploration perspective

The SVN plug-in of eclipse provides a perspective for the svn repository to work together. To activate this perspective, select Window> open perspective> other... and then select SVN repository tracing.

Introduction

This perspective consists of the svn repository view and history view. When you switch to this workbench, the svn repository view displays the svn repository address. The history view consists of three independent panels and lists the revision history of a specific resource (file or folder), if it has a SVN repository.

 

 

Overview of Group Synchronization perspective

When you manipulate a multi-module project in a team, the impact of your changes associated with the changes submitted by others may be very uncontrollable. To solve this problem, Eclipse IDE provides the Group Synchronization perspective, and the svn plug-in of eclipse has this extension to support the svn repository. To activate this perspective, select Window> open perspective> other... and then select team synchronizing. Of course, you can also go to the perspective view more quickly through the context menu items of team> synchronize... in your work copy.

Group syncIs a concept, it is cross-resource, it takes your existing work copy as the focus, at the same time in three ways to merge all the changes you may involve, then, filter required messages before performing any update and submission. Your local changes are calledOutbound", And the last update in the repository is called"Transfer". In the synchronization perspective, the outbound and inbound changes are inBefore SynchronizationAnalyzed together; more accurately, for local changes, synchronization means updating the repository changes to your work copy (equivalent to team> Update). For outgoing changes, synchronization means that your local changes have been submitted to the repository.

The Startup Group Synchronization perspective does not automatically update (or change) the local status or repository resources.

The Group Synchronization perspective is similar to outputting SVN status-u in the command line.

The Group Synchronization perspective is a feature of Eclipse IDE. For more details about group synchronization, refer to the CVS workspace synchronization help.

 

View content

• Annotation View
• Control View
• History View
• Attribute View
• Repository View

SVN annotation View

This view can beTeam> show AnnotationMenu access. You can also chooseWindow> Open View> other..., SelectSVN> SVN annotate ViewTo activate the view. This view is also part of the Group Synchronization perspective.

 

Function

SVN annotation ViewYesSVN repository exploration perspectiveIt allows you to check the revision history of a specified file, left-click to reach individual lines in the code.

This view consists of three completely separated regions:

• The first pane lists all the individual records for the change to the selected file, including the number of lines changed by the code corresponding to the revision number and revision number.
• The eclipse text browser displays the content of the selected file according to the revision.
• Contains the historical view of the selected file.

The dynamic relationship between the history view and file content view and the Revision Panel. On the Revision Panel, left-click an entry and all the modified rows for this revision are highlighted in the file in the text view. If you select a line in the Text View, the revised person is highlighted in the Revision Panel. The history view is automatically changed based on each selected revision number to provide their complete details.

 

 

SVN control View

 

Function

The SVN console view displays the communication between your client and the svn repository. The output is expressed by sending commands to the svn server and simulating the svn command line. Many workbench parameters can be set when controlling the output of the svn console.

Toolbar

 Clear Console

 

Clear the output of the current Console window.

 Scroll lock

 

Once activated, the console window will be blocked from rolling the output of new information to the end of the list.

Pin Console

 

Prevents console windows from jumping to active processes.

Display Console

 

Switch the console to a process you selected.

Open Console

Open another console window.

 

History View

This view can beTeam> show historyObtain the context menu. Subclipse uses the common group history view and the framework provided through eclipse. You can also trigger this view in another way, selectWindow> show View> other...And then selectTeam> history.

 

Function

This view shows the history of the selected resource, if it still exists in the svn repository. In SVN, both files and directories are versioned and have a historical track. If the selected resource is in the work copy, the current revision is highlighted (BOLD ).

This view consists of three completely separated regions:

• The revision form displays the revision number, date/time of the revision, name of the modifier, and submission information in the first column. You can click any revision number to display all its details.
• Modify the affected resource list (modify, add, delete, or change attributes ).
• Submission of the selected revision.

Get File/Contents

Updates and/or revisions to local resources.

 

Show differences

You can request to view the revision history of any file or folder in the svn repository.

 

Revert

You can roll back the changes of a specified revision to effectively cancel the changes that have been completed.

 

Branch/Tag

Check the repository address as a working copy to your local workspace.

 

Update commit messages

You can update the submitted content (submission information, Submitter, and so on) through the specified revision (submission) operation ).

 

View Annotation

View the revision history of a specific line in a code/text file.

 

Compare

Compare two specified file revisions.

Toolbar

 
Refresh

Refresh the display content of the current resource history.

 
 Next NN

By default, the resource history view only loads the latest revision to the Revision Table. The revision number is returned through SVN parameter settings. This command retrieves the next revision from the repository.

 Get all

This command Retrieves all revisions from the repository's selected resources.

Link with Editor

History ViewYou can link to the current editor. Once linked, You can edit the content that you change when you change the resource when you change the table. Displaying the resource history may be a long running operation because it retrieves the repository. If a remote repository works on the same Wan or internet, you may want to disable the "link to editor" button. Otherwise, the view is explicitly disabled or hidden when you switch to the resource editor.

 
 Options

This command displays a menu of view options to control behavior and display the Historical View.

Context Menu

Any entries listed in the Revision Table have an available context menu.

The available menu items in the context menu depend on whether you trigger the process from your work copy to the resource history view, orSVN repository ViewChanges to the resource history view.

Get Contents

Use this option to update the content of the Repository revision to the file selected for your work copy. The revision number of your local file will not be changed using this option. This option is valid only when the resource history is activated as a separate file in the local working copy.

Get Revision

Use this option to copy the revision selected in the repository to replace the file in your working copy. The revision number of your local file is changed to the selected revision. This option is valid only when the resource history is activated as a separate file in the local working copy.

Create uniied diff

This menu item creates an output file in a unified format for changes to the selected revision. Used to compare selected revisions with previous ones.

Create branch/tag from revision

Using this option creates a branch or tag in the repository based on the currently selected revision.

Set commit Properties

This option will allow you to update attributes associated with a specific submission operation (Revision description, revised by, and so on ).

Revert changes from revision

Use this option to undo the changes made to the selected revision. This option is valid only when the resource history is activated to a local working copy.

Show Annotation

This option is activated from the selected file to the svn comment view. This comment view allows you to view the revision history of specific code (text) in a file. This option is valid only when the resource history is activated as a separate file in the local working copy.

Compare

Use the default comparison view specified in your eclipse workbench preferences to compare the revisions selected in the file. This option is valid only when the resource history is activated as a separate file in the local working copy.

 

SVN attribute View

This view can be directly accessed through the "Team> show properties" menu. Of course, you can also select Window> Open View> other..., and then select SVN... SVN properties to enable this view.

 

Function

The SVN attribute view lists all SVN attributes related to a selected resource and allows you to add, modify, and delete them.

In general, attributes are only arranged by key/value pairs, which means that some things correspond to special purposes in the repository. However, some features are clear, which is especially important for SVN itself and the user interface (such as the eclipse SVN plug-in. Attribute itself is versionized data, so if you want to change an attribute, You need to submit it before others view it.

Context Menu refresh View

Refresh the svn attribute view to update and display the latest information in the repository.

Add/modify a property

 

This option activates the "set a SVN property" panel.

Save property value

Allows you to save property values to a file in the current or alternative project.

Delete Property

 

Delete attributes (keys and values) from the selected resource ). Confirmation is required before a deletion request is submitted.

 

 

SVN repository View

SVN repository ViewYesSVN repository exploration perspective.

 

Function

The SVN repository view allows you to define and manage SVN repository addresses on the eclipse workbench. The repository files and folders exist in a tree view. The top-level node in the tree view represents a connection to a specified SVN repository address. Once you define such an address, you can access a series of repository operations, including:

History

You can request to view the revision history of any files or folders in this repository.

Checkout

Check the repository location to your local workbench as a working copy.

Import/Export

Directly import the data from the local or network resource location to the repository, and vice versa, export a selected resource from the repository.

New, rename, delete

You can directly manipulate the repository resources in this view, including creating new folders, renaming and deleting files (folders ).

Branch/Tag

Creating a branch or marking a repository resource is just a simple operation.

Copy, paste

The copy and paste function allows you to copy a single file or the entire folder in the repository.

Relocate

Migrate Your repository due to IP address updates, protocol changes, or similar reasons.

Compare

You can select two files or folders to compare them in a uniform differential file mode.

Tool bar

Home

Reset the view to the top layer and retain the focus of the current position.

Back

When"Go"Run the command to enter the hierarchical view and use this command to exit.

Go

Enter the selected folder and make it to the top of the inbound level.

 

Refresh

Refresh the content of the view.

 

Collapse all

This command shrinks the tree extension status of all resources in the view.

 
Add SVN Repository

This command will generate a wizard for "Add a new SVN repository.

Context Menu

The context menu options may be slightly different, depending on the entries selected in the svn repository view.

New> new remote folder

"
New remote folder wizard.

New> repository location

The new SVN repository wizard is generated for this menu.

History

This menu item displays the historical revision history of the selected file or folder in the history view.

Create uniied diff

This menu item allows two files or folders to be selected for comparison. The output result of the comparison is saved to a file in a unified differential format.

Check out

If a. project file is found in the selected directory, check out as project is a foreseeable option. This option will create a working copy in a new folder of your active workbench. If you want to create a work copy elsewhere in your active workbench, you can use the check out as project into option. Then you can specify an alternative location to store the working copy. If no. project file exists in the selected directory, you can use the check out as... option. This option allows you to specify the project type you want to create, check out the files in the repository address, and then create a. Project for your work copy.
File.

Export

 

Export (copy) the selected resource to a specified target location.

Import

Import a local or network resource to the repository.

Rename/move

This option will generate the "move or rename a remote resource" Wizard.

Branch/Tag

This option allows you to complete the branch and tag process as a single operation step, which simplifies the copy and paste of the Repository resources.

Copy/paste

These options allow you to copy and paste files and folder Resources in the repository. Pasting is a submission operation. You will be notified to enter an explanation (comment) for the part of the pasting process ).

Delete

This delete option removes the selected resource from the repository. You can delete one or more selected files (folders) in a single operation ). To select multiple resources, press shift or Ctrl and click the resource you want to delete. The delete operation is a submission operation. You will be notified to submit an explanation (comment) for the part of the deletion process ).

Copy URL to clipboard

This option copies the complete repository address of the selected resource to the Windows clipboard. If you want to share the address with your colleagues, or copy the address to an email, document, or similar text, it is always useful.

Properties

This option displays the attributes of the selected repository resource, including the URL, last modifier, revision number, and date.

Refresh View

Refresh the svn attribute view to update and display the latest information in the repository.

Relocate

If the server IP address or protocol is changed (for example, http: // to https ://) or, if the path of the Repository directory on the server device changes, or the address of the Repository directory changes, use this migration command.