Skip to content

Supporting Indigo

Jump to bottom
reprogrammer edited this page Jul 1, 2011 · 13 revisions

Download Eclipse Indigo

  1. Download the Indigo version of Eclipse for RCP and RAP Developers from http://www.eclipse.org/downloads/packages/eclipse-rcp-and-rap-developers/indigor.

Check out the plug-in to patch

  1. Switch to the indigo branch for CodingSpectator.
  2. Ensure that any plug-ins you check out will be in the plug-ins/indigo directory.
  3. Go to the "Plug-ins" view of Eclipse and select the plug-in you'd like to patch. Then, right click on the plug-in and select Import As > Project from a Repository...
  4. In the "Import Plug-ins and Fragments" dialog, select "Import the indicated version" (this is the default).
  5. Clean the workspace and ensure that "Build Automatically" is not selected. This prevents Eclipse from generating any javadocs, html files, etc that could be mistakenly added to the initial commit.
  6. Commit the checked out version of the plug-in into the git repository of CodingSpectator at "plug-ins/indigo". It's all right to include the CVS metadata files. Please include the version of the plug-in that you're committing in the commit message.
Initial commit of xxx.xxx.xxx 

v2011xxxxxx-xxxx

This commit belongs to issue #206.

Check out the UDC plug-ins to patch

The source code of UDC plug-ins reside in a different CVS repository. Thus, you cannot check the source of UDC plug-ins from the "Plug-ins" view. To check out the source code of UDC plug-ins used in Indigo take the following steps.

  1. Add the CVS repository :pserver:anonymous@dev.eclipse.org:/cvsroot/technology to the "CVS Repositories" view of Eclipse.
  2. Browse to the HEAD/org.eclipse.epp folder inside the CVS repository.
  3. Right-click on the org.eclipse.epp folder and select "Configure Branches and Versions...".
  4. Open the MANIFEST.MF file of one of the org.eclipse.epp.usagedata.* plug-ins. Some checked tags should appear in the area entitled "New tags found in the selected files:".
  5. Click on the "Add Checked Tags" button.
  6. Click on the "OK" button.
  7. Browse to Versions/org.eclipse.epp/org.eclipse.epp INDIGO_R inside the CVS repository.
  8. Find and check out the org.eclipse.epp.usagedata.* plug-ins tagged as INDIGO_R.

Patch the plug-ins

  1. First you would need to disconnect the packages from the CVS directories. This prevents Eclipse from generating extra CVS metadata after we apply the patches. Right-click on the plug-in in Eclipse, select Team > Disconnect...
  2. In the dialog that pops-up, do not delete the the CVS metadata. This allows us to reconnect to CVS, if necessary.
  3. Navigate to the root directory of CodingSpectator.
  4. Select the plug-in that you wish to generate a patch for.
  5. git log directory-of-plugin where directory-of-plugin is like org.eclipse.ltk.core.refactoring
  6. Scroll to the bottom of the log and note the SHA for the initial commit. Call this InitialSHA.
  7. git diff --no-prefix InitialSHA master directory-of-plugin > someFile.patch
  8. Navigate back to the Eclipse
  9. Right-click on the plug-in to patch and select Team > Apply Patch...
  10. Choose someFile.patch that was generated in the previous steps.
  11. In the next dialog, select "Apply the patch to the workspace root". This step is very important – if you don't select the workspace root, the patch will not apply!
  12. In the "Apply Patch" dialog, exclude all changes to bin. Select the changes to bin, right-click on them and select "Exclude".
  13. In the "Appli Patch" dialog, mark the "Generate a .rej file for unmerged hunks". Reject files will help you manually patch the files that Eclipse has failed to fully patch.
  14. Review the changes and check that the patch can apply cleanly. Any changes that cannot be applied cleanly should be performed by hand.
  15. Commit the patched version
Patched xxx.xxx.xxx 

This commit belongs to issue #206.
Clone this wiki locally