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.
SWT/Devel/Workflow
Contents
Preserving run configurations across workspaces
If you are using the same major version of Eclipse across workspaces, you can copy your run configurations across to prevent losing them. It's highly recommended that you backup your workspace before copying, in case something goes awry.
To find your current launch configurations, navigate to:
<workspace directory>/.metadata/.plugins/org.eclipse.debug.core/.launches
In this folder, there should be a .launch file for every run configuration created within Eclipse. Copy all these files to:
<new workspace directory>/.metadata/.plugins/org.eclipse.debug.core/.launches
Launch Eclipse using the new workspace. Open the run configurations dialog, all the old run configurations should be there.
Using Gerrit
Gerrit is used to review your patches. For further information, please see gerrit.
Backporting Patches
You have several options. 1) On the gerrit review of your patch, click on 'cherry pick' and start typing the name of your branch (e.g R4_5_maintenance) 2) Check out the remote repository locally, manually cherry pick the commit from your git history, then do either one of:
3a) Push directly into branch
If you have committer rights and you would like to push your patch directly into a backport branch, execute from command line as following:
git push review HEAD:R4_5_maintenance
3b) Create a review for backport
If you would like to submit an extra gerrit review before merging into a backport branch, execute as following:
git push review HEAD:ref/for/R4_5_maintenance
(Note, the 'ref/for/' is a branch that gerrit monitors to create new patch reviews.)
Mylyn
Nice Video tutorials:
- Mylyn overview: Youtube : Mylyn Overview
- Mylyn, doing code reviews on gerrit Youtube : Code review inside Eclipse with gerrit
Note, you need to install the 'Gerrit' connector inside mylyn.