The Java introduction page gives a basic instruction on the working environment here at ISIP.

Introduction:

To access a Java file for editing, open a new terminal and go to the file's directory. In the example, the user should enter their directory to the right of the "/users" directory. Also, the user might have to ssh in depending on where the file is stored.

	Ex:
	 Juno_[02]:ssh isip006.isip.msstate.edu -l userName

	Ex:
	 Juno_[02]:sd /cavs/hse/data2/isip/users
	 /cavs/hse/data2/isip/users

Check Out:

At ISIP the standard way files are created, edited, and reposted is done with a simple checkin/checkout system. A user may want to edit a piece of code, so they would check out the files necessary. While the file is checked out, no one else can check out the file. This ensures that concurrent updating on the same file can occur.

	Ex:
	 Juno_[02]:isip_co AudioCircularBuffer.java
	 AudioCircularBuffer.java,v --> AudioCircularBuffer.java
	 revision: 1.13 (locked)
	 done

Editing:

The editor used at ISIP is Emacs. To open the Emacs editor do not enter the "emacs" command. Enter the command "isip_e" and the editor will open. It is common for the user to check out a file and edit it within their own directory and test it there.

	Ex:
	 Juno_[02]:isip_e AudioCircularBuffer.java

Check In:

After editing, the file must be checked back in. After running the "isip_ci" command, a log is prompted for changes made on the code while it was checked out. Each log entry must be followed by a period, and to end the log entries enter a period on a blank line. Prior to check in the file must be well documented.

	Ex:
	 Juno_[02]:isip_ci AudioCircularBuffer.java
	 AudioCircularBuffer.java,v <-- AudioCircularBuffer.java
	 new revision: 1.14; previous revision: 1.13
	 enter log message, terminated with single '.' or end of file:
	 >> Fixed bug in the isFull() method.
	 >> .
	 done

New File Creation:

In order to create a new file, the file can be created in one's own directory using the "isip_e" command. Once the code has been tested, debugged, and documented, it can be saved to the repository by using the "isip_ci" command in the desired directory.

Go to next page