The Xenei source code and other supporting files may be acquired two ways, through CVS (Concurrent Version System) or from the full product distribution files. If you are planning to add functionality you plan to contribute back to Xenei.org then the CVS approach is appropriate. However, if you are developing extensions you do not plan to contribute then the product distribution file approach may be best.

In the following examples the specific Xenei project name should be substituted where project is shown.

CVS access

SourceForge.net provides CVS services for Xenei projects. For additional information go to the CVS link on the Xenei site of the product(s) you are using. Each project's CVS page contains the necessary details for connecting to that CVS. Also, all Xenei projects are listed on the main http://www.xenei.org site.

Anonymous CVS Access

Xenei project's SourceForge.net CVS repositories can be checked out through anonymous (pserver) CVS with the following instructions. The module you wish to check out must be specified as the modulename. When prompted for a password for anonymous, simply press the Enter key. To determine the names of the modules created by the project, you may browse the CVS repository via the web-based CVS repository viewer provided on the CVS page for each project.

From Eclipse:

• Host: cvs.sourceforge.net
• Repository path: /cvsroot/project
• User: anonymous
• Password: Press Enter when prompted
• Connection type: pserver

From command-line:

• cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/project login
• cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/project co modulename

Information about accessing the Xenei projects CVS repositories may be found on SourceForge.net in the document titled, " Basic Introduction to CVS and SourceForge.net (SF.net) Project CVS Services ".

Updates from within the module's directory do not need the -d parameter.

Developer CVS Access via SSH

Only project developers may access the CVS tree via this method. A SSH client must be installed on your client machine. Substitute modulename and developername with the proper values. Enter your site password when prompted.

A significant amount of information about project CVS services may be found on SourceForge.net in their " Introduction to SourceForge.net Project CVS Services for Developers ". Developers new to CVS should read their " Basic Introduction to CVS and SourceForge.net (SF.net) Project CVS Services ".

Developers may also make use of shared SSH keys for authentication.

From Eclipse:

• Host: cvs.sourceforge.net
• Repository path: /cvsroot/project
• User: registered_developer_name
• Password: registered_developer_password
• Connection type: extssh

From command-line:

• export CVS_RSH=ssh
• cvs -z3 -d:ext:developername@cvs.sourceforge.net:/cvsroot/project co modulename

CVS check-out using Eclipse

Eclipse contains a nice CVS implementation that connections directly to the SourceForge.net repositories. Each folder in the project's CVS is a separate Eclipse project, except CVSROOT. Some may also have a directory containing multiple projects, such as the Xenei project's incubator .

Start Eclipse and open the CVS Repositories view.

• Right-click in the view, select New , then Repository Location... .
• Enter the parameters as listed above or from the project's SourceForge.net CVS page.
• Open the products CVS, then the HEAD section and select each folder in turn, except CVSROOT .
• Right click on the folder and select Check out as... .
• Change the project name to something that reflects the build.support directory in the current development environment.
• Uncheck Use default workspace location .
• In the location select the Xenei.root directory.
• Eclipse will add the project name to the directory name. The directory name may be edited for readability and usability. Click OK .
• Repeat the process for each CVS folder (project), except CVSROOT .

CVS check-out using the command-line

For detailed information about the use of command-line CVS please see its associated documentation.

• Set the CVSROOT environment variable according to the instructions in CVS access above.
• cvs -z3 co modulename

Installing the product distributions

Xenei product distributions use this naming convention: productName_version_buildDate.zip . Most projects also offer a minimal distribution containing updates and additions, and a src or source-only distribution. For development purposes the file NOT named as minimal or src is the full distribution containing everything needed to execute the product, if applicable, and to re-build the product.

Important Note: All Xenei product distribution files are built with the preset Xenei.root directory xenei for consistency. If you are using a different directory name for Xenei.root then once a Xenei product distribution is unpacked into directory xenei either rename it, or move the newly created subdirectories to the desired location. The layout of the subdirectories must be maintained.

To install a Xenei product from its distribution file:

• Change to the directory above where you want the xenei directory to be created.
• unzip productFile

The Xenei project directories

Each Xenei project that will be part of the development effort in this environment should be acquired per the instructions above. It is important to name the projects something that reflects the fact that they are part of this development environment.

In Eclipse, when a different project name is used than that used when the project was last checked-in, the names of the Required Projects needed by some projects may need to be changed.