PDT/Development Environment

Understanding the CVS Structure

If you are unfamiliar with CVS concepts, there is a good list of resources on the CVS repository page.

Modules structure

The EMF, SDO and XSD sources are divided into three modules in CVS.

CVS Repository	Module	Directories
/cvsroot/modeling	org.eclipse.emf/org.eclipse.emf
		plugins	contains the EMF plug-ins
		features	contains the EMF features
		doc	contains the EMF documentation plug-ins and features
		tests	contains the EMF, SDO and XSD automated tests plug-ins and features
		examples	contains the EMF examples
/cvsroot/modeling	org.eclipse.emf/org.eclipse.emf.ecore.sdo
		plugins	contains the SDO plug-ins
		features	contains the SDO features
		doc	contains the SDO documentation plug-ins and features
/cvsroot/modeling	org.eclipse.mdt/org.eclipse.xsd
		plugins	contains the XSD plug-ins
		features	contains the XSD features
		doc	contains the XSD documentation plug-ins and features
		examples	contains the XSD examples

EMF and SDO are components of the EMF Project. XSD is a component of the MDT Project.

Build tag and branch naming conventions

For each build, a new CVS tag is created. The name of the CVS tag follows this convention:

build_<build id>

where <build id> is usually the build timestamp in the yyyyMMddhhmmss format (for example, 20040211140643).

The HEAD branch always contains the latest file versions, which are currently under active development. If a fix is required for a particular past build (typically a release), a branch will be created. The branch naming convention is:

branch_<build id>

The structure of the CVS repository is shown below:

If for some reason you need to get files from a certain build, look under "Versions" for the tag that identifies that build.