CVS Connections have their own Navigator Window in JDeveloper. You can browse both local and remote pserver or ssh repositories directly from the CVS Navigator. Many other operations including opening files and checking out a module are also available.

JDeveloper has always maintained an internal registry of known file types (such as JAVA, JPG, GIF, PNG, etc). This registry has been extended to include if a file is binary or not. CVS uses this file type information when importing and adding new files to a CVS repository. This reduces the need to supply this information regularly.

Whenever you perform a refactoring operation (such as move class, rename class, or any others), the VCS support will automatically handle the underlying source control system. If you are using a VCS system such as Clearcase which understands renaming of elements, a "cleartool mv" will happen under the covers. If your VCS system doesn't support this, such as CVS, then a remove and an add will be executed on your behalf.

As will all VCS commands, JDeveloper displays the actual commands issued.

After you commit a file, JDeveloper will remember the last couple of comments you used and offer them again. If you leave "Use Comment Templates on Commit" selected in the CVS General preferences (this is the default setting), this option is not enabled.

If there are files not added to CVS when you commit files in your module, JDeveloper will ask if you would like to add these files. This helps ensure that nothing is left behind when you commit your changes (and you don't risk breaking the build!)

The previous "Uncommitted Files" window used to simply list files scheduled for commit in CVS. Now this window has been renamed to "Pending Changes" and lists:

1. Outgoing - Files modified Locally which need to be checked into the source control system
2. Incoming - Files modified by another user of the source control system that are newer than the revisions currently checked out.
3. Candidates - Files which are not currently under source control and should possibly be added.

JDeveloper makes periodic backup copies of each file to provide an offline "local" history of your changes. This list of changes is merged in with the changes from the VCS system to provide a unified history view of each file you work with. Any comments from your source control system is displayed for the description of each revision.

Not only can you see the history of a file, but JDeveloper also provides a graphical difference tool integrated with the history of each file. From here you can edit the right-hand-side or use your mouse to remove blocks of differences by clicking on the large red X icons.

For ease of use when using JDeveloper and external CVS tools, you can choose "Copy CVSROOT" from the context menu for each repository connection in the CVS Navigator.

JDeveloper can create a patch at any time, and apply patches when using CVS. This enables easy collaboration with Open Source projects. The patches created can either be written out to a file, or put into the system's clipboard for pasting into an email message or instant message.

When you apply a patch, it can come from either the clipboard or a file.

JDeveloper will ask for the location of the new repository and also ask if you would like a new CVS connection created for this repository.

Here you can see a new connection is created for the new local CVS repository:

JDeveloper includes an internal CVS and SSH client both written in Java. We can also create a public/private key pair using the RSA or DSA algorithms. If CVS is not installed and locatable on your PATH, the internal CVS client is used automatically.

The Checkout Module command has been simplified to only ask the most common questions. If you need to checkout based on a date or other advanced option, you may enabled "Advanced Mode" from the Versioning Menu to see more options.

JDeveloper provides a property sheet with all of the VCS specific properties associated with a file under source control. This includes information such as; revision, status, last modification, and associated tags. You can access this property sheet from the menu command Versioning > Properties