Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "PDT/Development Environment"

< PDT
(New page: ==Understanding the CVS Structure== If you are unfamiliar with CVS concepts, there is a good list of resources on the [http://dev.eclipse.org/viewcvs/index.cgi/?cvsroot=Modeling_Project C...)
 
(Modules structure)
 
(11 intermediate revisions by the same user not shown)
Line 1: Line 1:
==Understanding the CVS Structure==
+
==Understanding the GIT Structure==
  
If you are unfamiliar with CVS concepts, there is a good list of resources on the [http://dev.eclipse.org/viewcvs/index.cgi/?cvsroot=Modeling_Project CVS repository] page.
+
If you are unfamiliar with GIT and Gerrit concepts, there is a good list of resources on the [https://wiki.eclipse.org/Development_Resources/Contributing_via_Git#via_Gerrit eclipse contributing page].
  
 
===Modules structure===
 
===Modules structure===
  
The EMF, SDO and XSD sources are divided into three modules in CVS.
+
There is one module of the Eclipse PDT project in GIT.
  
 
<table cellspacing="0" cellpadding="5" border="1">
 
<table cellspacing="0" cellpadding="5" border="1">
 
<tr>
 
<tr>
<td><b>CVS Repository</b></td>
+
<td><b>GIT Repository</b></td>
<td><b>Module</b></td>
+
 
<td colspan="2"><b>Directories</b></td>
 
<td colspan="2"><b>Directories</b></td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<td rowspan="6" valign="top">/cvsroot/modeling</td>
+
<td rowspan="6" valign="top">/gitroot/tools/org.eclipse.pdt.git</td>
<td rowspan="6" valign="top">org.eclipse.emf/org.eclipse.emf</td>
+
 
</tr>
 
</tr>
 
<tr>
 
<tr>
 
<td>plugins</td>
 
<td>plugins</td>
<td>contains the EMF plug-ins</td>
+
<td>contains the PDT plug-ins</td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<td>[[EMF_2.3_New_Features_Migration_Guide | features]]</td>
+
<td>features</td>
<td>contains the EMF features</td>
+
<td>contains the PDT features</td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
 
<td>doc</td>
 
<td>doc</td>
<td>contains the EMF documentation plug-ins and features</td>
+
<td>contains the PDT documentation plug-ins and features</td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
 
<td>tests</td>
 
<td>tests</td>
<td>contains the EMF, SDO and XSD automated tests plug-ins and features</td>
+
<td>contains the PDT automated tests plug-ins and features</td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
 
<td>examples</td>
 
<td>examples</td>
<td>contains the EMF examples</td>
+
<td>contains the PDT examples</td>
</tr>
+
<tr>
+
<td rowspan="4" valign="top">/cvsroot/modeling</td>
+
<td rowspan="4" valign="top">org.eclipse.emf/org.eclipse.emf.ecore.sdo</td>
+
</tr>
+
<tr>
+
<td>plugins</td>
+
<td>contains the SDO plug-ins</td>
+
</tr>
+
<tr>
+
<td>[[EMF_2.3_New_Features_Migration_Guide | features]]</td>
+
<td>contains the SDO features</td>
+
</tr>
+
<tr>
+
<td>doc</td>
+
<td>contains the SDO documentation plug-ins and features</td>
+
</tr>
+
<tr>
+
<td rowspan="5" valign="top">/cvsroot/modeling</td>
+
<td rowspan="5" valign="top">org.eclipse.mdt/org.eclipse.xsd</td>
+
</tr>
+
<tr>
+
<td>plugins</td>
+
<td>contains the XSD plug-ins</td>
+
</tr>
+
<tr>
+
<td>[[EMF_2.3_New_Features_Migration_Guide | features]]</td>
+
<td>contains the XSD features</td>
+
</tr>
+
<tr>
+
<td>doc</td>
+
<td>contains the XSD documentation plug-ins and features</td>
+
</tr>
+
<tr>
+
<td>examples</td>
+
<td>contains the XSD examples</td>
+
 
</tr>
 
</tr>
 
</table>
 
</table>
  
EMF and SDO are components of the [http://www.eclipse.org/modeling/emf/ EMF Project]. XSD is a component of the [http://www.eclipse.org/modeling/mdt/ MDT Project].
+
===Build tag and branch naming conventions===
 +
 
 +
The structure of the GIT repository is shown below:
 +
 
 +
[[Image:PDT_SetupDev_CVS_Structure.png]]
 +
 
 +
==Checking Out Code as an Anonymous User==
 +
 
 +
An anonymous user has access only to check out files from the GIT repository. This user does not have the privileges to check in files.
 +
 
 +
===Configuring the GIT client to check out files===
 +
 
 +
* Open the GIT perspective in the Eclipse Workbench by selecting <b>Windows > Open Perspective > GIT</b>. 
 +
 
 +
* Right click on the GIT Repositories view, and select <b>New > Repository Location...</b>
 +
 
 +
  Clone URI: git clone http://git.eclipse.org/gitroot/pdt/org.eclipse.pdt.git
 +
  # or if you're eclipse user and/or PDT committer: git clone ssh://committerid@git.eclipse.org:29418/pdt/org.eclipse.pdt.git
  
===Build tag and branch naming conventions===
 
  
For each build, a new CVS tag is created. The name of the CVS tag follows this convention:
+
==Checking Out Code ==
  
build_&lt;build id&gt;
+
If you followed the instructions in the previous section, you should see a new repository entry in the GIT Repositories view.
  
where &lt;build id&gt; is usually the build timestamp in the yyyyMMddhhmmss format (for example,  20040211140643).
+
To check out code, you have two options. Either check out the projects automatically using a [[#Using Team Project Set File (.psf)|Team Project Set File]], or [[#Manual Checkout|manually]].
  
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:
+
===Using Team Project Set File (.psf)===
  
branch_&lt;build id&gt;
+
* Download the [https://git.eclipse.org/c/pdt/org.eclipse.pdt.git/tree/dev/psf/pdt-dev.psf 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.
  
The structure of the CVS repository is shown below:
+
* Browse for the .psf file you want to use. Click Finish.
  
[[Image:EMF_SetupDev_CVS_Structure.png]]
+
* Each feature & plugin will then be checked out as a project in the workspace.
  
If for some reason you need to get files from a certain build, look under "Versions" for the tag that identifies that build.
+
[[Category:PDT]]

Latest revision as of 16:53, 15 August 2015

Understanding the GIT Structure

If you are unfamiliar with GIT and Gerrit concepts, there is a good list of resources on the eclipse contributing page.

Modules structure

There is one module of the Eclipse PDT project in GIT.

GIT Repository Directories
/gitroot/tools/org.eclipse.pdt.git
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

The structure of the GIT repository is shown below:

PDT SetupDev CVS Structure.png

Checking Out Code as an Anonymous User

An anonymous user has access only to check out files from the GIT repository. This user does not have the privileges to check in files.

Configuring the GIT client to check out files

  • Open the GIT perspective in the Eclipse Workbench by selecting Windows > Open Perspective > GIT.
  • Right click on the GIT Repositories view, and select New > Repository Location...
 Clone URI: git clone http://git.eclipse.org/gitroot/pdt/org.eclipse.pdt.git
 # or if you're eclipse user and/or PDT committer: git clone ssh://committerid@git.eclipse.org:29418/pdt/org.eclipse.pdt.git 


Checking Out Code

If you followed the instructions in the previous section, you should see a new repository entry in the GIT 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.

Back to the top