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 "SWT/Devel/Workflow"
m (→Backporting Patches) |
|||
| Line 30: | Line 30: | ||
= Backporting Patches = | = Backporting Patches = | ||
| − | You have several options | + | You have several options: <br> |
| − | 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) | + | 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) <br> |
| − | 2) Check out the remote repository locally, manually cherry pick the commit from your git history, then do either one of: | + | 2) Check out the remote repository locally, manually cherry pick the commit from your git history, then do either one of: <br> |
| − | + | ||
3a) '''Push directly into branch''' | 3a) '''Push directly into branch''' | ||
Revision as of 09:55, 11 July 2016
Contents
Launching Eclipse with SWT source code
To test SWT snippets, it's useful to launch a child Eclipse with your patch to see how it looks and feels. To do so, under run-configurations, right click on "Eclipse Application" and select "new".
Common troubleshooting
Often Eclipse won't launch with various errors. Below are common steps to troubleshoot.
- API Baseline: Make sure API Base line is set. If you updated Eclipse (e.g Luna to Mars), you may need to re-create the baseline.
- Enable Execution Environments: Make sure that relevant Execution Environments are enabled. (1.5, 1.6 etc..)
- Target Platform: Make sure to have an Target Platform set. Try re-creating it with Default for running platform.
- Validate Plugins: In the run-time configuration for a Child Eclipse, under the 'Plug-ins' tab, instead of launching all plugins, try to select only SWT and it's binaries. Try to Validate the setup to see if there are missing dependencies.
- re-create new run-time configuration: Often after updating Eclipse version, I have to create new "Eclipse Application" run time configurations for the child Eclipse to launch propertly
Tips
- Choice of child Eclipse Workspace: Instead of using a blank workspace, copy your exiting workspace, append '-runtime' and use that for your child Eclipse.
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.