Source Control for jEdit

Version: 0.7.1

Author: Stuart Barlow

Maintainer: Mirco Bova

With credit to:

Contributors:

This is a simple plugin to allow the control of the current file in a source control system. At present we have the MS Visual Source Safe, Source Off Site, Perforce and CVS systems integrated. Please feel free to donate modules for other source control systems.

General Options

Source Control System

Used to select the Source Control system.

Prompt Before Checkout

If you are bugged by allways getting prompted then un-check this.

Checkout Comment

Default comment used for checkout and checkin.

Visual Source Safe Options

You may have multiple VSS projects configured to different working directories. Or you may just set the root of VSS ($/) to point to a single working directory.

VSS Win32 Directory

This is the directory that your VSS executable (ss.exe) lives in.
example: \\machine_name\directory\win32

VSS DB Directory

This is the directory that your VSS Database lives in. This is the folder where srcsafe.ini is placed.
example: \\machine_name\directory\share

VSS username and password

These are the username and password you use to access the above VSS db.
WARNING: the password is stored clear in jEdit props file.

VSS Projects

These are the VSS projects that you wish to work on within jEdit. You will need to set the project name (this must begin with $) and the working folder. At the most basic level you could map the root of VSS to the top level of a drive. You will then have only this single project mapping.

Examples

project name: $/ working folder: k:\vss_work
project name: $/ working folder: k:\
project name: $/jEdit/current/devel working folder: W:\java\development\jEdit\devel

Perforce Options

There is no options panel for this integration. Just some simple rules to follow.

The module assumes that the "p4" executable is in JEdit's PATH, and also that the right environment variables are set up so that P4 can run. These are generally "P4PORT", "P4CLIENT", and "P4USER".

If you have difficulties with this then please respond.

CVS Options

There is no options panel for this integration. Just some simple rules to follow.

The module assumes that the "cvs" executable is in JEdit's PATH, and also that the files you want to work on are already checked out (eg. with TortoiseCVS on Win32).

CVS uses a different naming convention for the various actions than SourceControl:

		CVS                        SourceControl
		------------------         ------------------------
		checkout                   get
		edit                       checkout
		unedit                     undo checkout

If you have difficulties with this then please send email to the maintainer.

How to Add a new Source Control System

First add the system type to the SourceControl.props file in the key...

options.sourcecontrol.sctypes

Then create a class that implements the com.sgbarlow.sourcecontrol.SourceControlInterface interface.
Your class must have name equal to the name you give your Source Control system with the spaces removed and Impl added to the end.
i.e. MS Visual Source Safe becomes MSVisualSourceSafeImpl

TODO

Change Log