Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "PDT/Development Environment"
Roy.zend.com (Talk | contribs) |
Roy.zend.com (Talk | contribs) (→Using Team Project Set File (.psf)) |
||
| Line 80: | Line 80: | ||
===Using Team Project Set File (.psf)=== | ===Using Team Project Set File (.psf)=== | ||
| − | * Download the [http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse. | + | * Download the [http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.pdt/releng/psf/?root=Tools_Project PSF file] and save it somewhere memorable, like your desktop. |
* Back in Eclipse, switch to the Java perspective. | * Back in Eclipse, switch to the Java perspective. | ||
* From the File menu or Project Explorer context menu, select '''Import'''. | * From the File menu or Project Explorer context menu, select '''Import'''. | ||
Revision as of 15:41, 26 June 2008
Contents
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
There is one module of the Eclipse PDT project in CVS.
| CVS Repository | Module | Directories | |
| /cvsroot/tools/ | org.eclipse.pdt | ||
| plugins | contains the PDT plug-ins | ||
| features | contains the PDT features | ||
| doc | contains the PDT documentation plug-ins and features | ||
| tests | contains the PDT automated tests plug-ins and features | ||
| examples | contains the PDT examples | ||
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:
Checking Out Code as an Anonymous User
An anonymous user has access only to check out files from the CVS repository. This user does not have the privileges to check in files.
Configuring the CVS client to check out files
- Open the CVS perspective in the Eclipse Workbench by selecting Windows > Open Perspective > CVS Repository Exploring.
- Right click on the CVS Repositories view, and select New > Repository Location...
- Enter the information in the Add CVS Repository dialog and click Finish. This will establish a connection with the /cvsroot/tools repository located on dev.eclipse.org, using the anonymous user ID. Make sure you set the connection type to pserver and use the default port, as shown.
- Host: dev.eclipse.org
- Repository path: /cvsroot/tools
- User: anonymous
- Connection type: pserver
Checking Out Code
If you followed the instructions in the previous section, you should see a new repository entry in the CVS Repositories view.
To check out code, you have two options. Either check out the projects automatically using a Team Project Set File, or manually.
Using Team Project Set File (.psf)
- Download the PSF file and save it somewhere memorable, like your desktop.
- Back in Eclipse, switch to the Java perspective.
- From the File menu or Project Explorer context menu, select Import.
- Choose Team > Team Project Set, then click Next.
- Browse for the .psf file you want to use. Click Finish.
- Each feature & plugin will then be checked out as a project in the workspace.
Manual Checkout
- Switch to the CVS perspective if not already there.
- Expand the repository node.
- Expand the HEAD node, as shown below, to view all the modules in the repository.
- Scroll down and expand the
org.eclipse.pdtmodule. Select the subdirectories of the features, plugins, docs, tests, and examples directories that you want to retrieve. - Right click and select the Check Out menu option.
- Each selected directory as is checked out as a project in the workspace. Once the operation is complete, you can switch to the Java perspective to work with the projects.