Home > SQL Developer Concepts and ... > Using Versioning
SQL Developer provides integrated support for the Subversion versioning and source control system, and you can add support for other such systems as extensions by clicking Help, then Check for Updates. Available extensions include CVS (Concurrent Versions System) and Perforce. The SQL Developer documentation does not provide detailed information about the concepts and operations of such systems; it assumes that you know them or can read about them in the product documentation.
For information about Subversion, see http://subversion.tigris.org/
. For Subversion documentation, see http://svnbook.red-bean.com/
.
For information about Perforce, see http://www.perforce.com/
.
For the CVS manual (by Per Cederqvist and others), see http://ximbiot.com/cvs/manual/
.
To access the versioning features of SQL Developer, use the Team menu.
If you create any versioning repositories, you can use the hierarchical display in the Files navigator, which is marked by a folder icon. (If that navigator is not visible, click View, then Files.) You can also view a hierarchical display of repositories and their contents in the Versioning navigator.
Related Topics
About Subversion and SQL Developer
About Perforce and SQL Developer
SQL Developer Concepts and Usage
Before you can work with a Subversion repository through SQL Developer, you must create a connection to it. When you create a local Subversion repository, a connection to it is automatically created, and this can be seen in the Versioning navigator. You can subsequently edit the connection details.
To connect to an existing Subversion repository (if no connection to that repository exists), use the Versioning navigator, as follows:
If the Versioning navigator is not visible, click View, then Team, then Versioning Navigator.
Right-click the top-level Subversion node and select New Repository Connection.
Complete the information in the Subversion: Create/Edit Subversion Connection dialog box, including the URL of the existing repository.
Use the connection to access the repository.
Existing files must be imported into the Subversion repository to bring them under version control. Files are then checked out from the Subversion repository to a local folder known as the "Subversion working copy". Files created in (or moved into) SQL Developer must be stored in the Subversion working copy.
Files newly created within SQL Developer must be added to version control. Changed and new files are made available to other users by committing them to the SQL Developer repository. The Subversion working copy can be updated with the contents of the Subversion repository to incorporate changes made by other users.
Perforce uses a local directory structure to receive files that are going to be placed under formal source control. This location is called the "Perforce client workspace". Files created in (or moved into) SQL Developer must be stored in this location. Once files are in your Perforce client workspace, you bring them fully under source control by submitting them to a central location called the "Perforce depot". Files must be submitted to the Perforce depot before they can be versioned and accessed by other users.
For more information, see the "Versioning Applications with Source Control" chapter in Oracle Fusion Middleware User's Guide for Oracle JDeveloper, search for information about Perforce, and understand that you are using Perforce within SQL Developer and not JDeveloper.
CVS repositories can be created on a local PC or remote server. There can be more than one CVS repository. You need to create one or more CVS repositories.
Source files are held in a CVS repository. The source files in a CVS repository are grouped into modules. If you have new files, a wizard in SQL Developer will help you import them into the CVS repository and place them under version control. A copy is made of your original files and placed in a subdirectory (.backup) of the one from which you imported them.
Files to be worked on are checked out from the CVS repository. This makes a local copy of the files. You can see the contents of the CVS repository in the SQL Developer CVS Navigator and open read-only versions of files. You can then decide which files you want to check out and work on.
CVS creates a new directory populated with the copy of the source files. You can see the files in the System Navigator. You can also open them from here.
Source files have a status, depending on what operations have been carried out on them. A preference lets you choose whether the version control status of a file is shown in the System Navigator.
The Pending Changes window is displayed if you request Pending Changes, or when you initiate an action that changes the local source control status of a file. This window shows files that have been added, modified or removed (locally or remotely), files whose content conflicts with other versions of the same file files that have not been added to source control files that are being watched, and files for which editors have been obtained. You can use this information to detect conflicts and to resolve them where possible.
The Outgoing pane shows changes made locally, the Incoming pane shows changes made remotely, and the Candidates pane shows files that have been created locally but not yet added to source control. You can double-click file names to edit them, and you can use the context menu to perform available operations.