Platform UI/How to Contribute/CVS
Working with the older CVS repository.
Checking out the Plug-ins
There are three kinds of plug-ins, the actual code, test plug-ins, and example plug-ins. Using the CVS Repository at :pserver:email@example.com:/cvsroot/eclipse, they are listed under HEAD/platform-ui, HEAD/platform-ui-examples, and HEAD/platform-ui-tests.
We recommend using a recent integration build from the Eclipse Project download page to avoid compile errors due to older versions of SWT or one of the runtime bundles that we depend upon.
To check out everything from within Eclipse, do the following:
- Type Ctrl+3 followed by 'npfc' to narrow down to "New Projects from CVS".
- Hit Enter to open the wizard dialog, then select "Create new repository location", and click Next.
- Copy the following string without the quotes into the "Host" field: ":pserver:firstname.lastname@example.org:/cvsroot/eclipse".
- Click Next, select "Use existing module", scroll all the way down and multi-select platform-ui, platform-ui-examples, and platform-ui-tests.
- Click Finish to import all of our plug-ins into your workspace. A dialog asking to replace "org.eclipse.jface.databinding.examples" is expected (it appears in the tests and the examples module), just click "Yes" or "No", it doesn't really matter.
New in 3.6:If you know the plugins you are working with, you can use File > Import... >Plug-in Development>Plug-ins and fragments wizard to import plugins directly from the repository. See Plug-in Import.
To check out individual parts such as only data binding, or JFace, use Project Set Files. You can import the file into Eclipse via Ctrl+3, 'tpsi'. This will check out the necessary projects into your workspace. We provide Project Sets for committers and contributors and for HEAD and maintenance branches. Please file a bug if you would like to have other kinds of project set files added to that page.
Creating a Patch
To contribute a patch, open the Synchronize view, and set it up to synchronize your complete workspace with the CVS repository. Double-check your changes by looking at them using the compare editor (double-click on changed files in the Synchronize view). The changes should be minimal and without extraneous whitespace changes. Select the changed files and create a patch using the "Create Patch..." wizard from the context menu. Save the patch to a file called patch-<bugid>.txt and use the default settings (diff output format: unified, patch root: workspace). Then, attach this file to the bug. Added bonus points for also providing unit tests, which should be put into the same patch file - see the next section on unit tests.