Installing eGit in Eclipse and CodeWarrior for MCU10.4
Git is now my favorite version control system. Git and GitHub are very powerful, it has (nearly) all features I can think about, and best of all: As a distributed version control system, I can work with it, even if disconnected from the network .
There are many standalone and IDE integration available for Git. Beside of using TortoiseGit, I’m using the eGit Eclipse integration. This post is about how to install eGit in Eclipse, particularly in CodeWarrior for MCU10.4.Installation
I’m using screenshots with the Eclipse based CodeWarrior for MCU10.4.
The normal eGit update site is . Because the Eclipse version used by CodeWarrior for MCU10.4 is an older one, the current eGit version. You will likely receive an error “Missing requirement: Git Team Provider UI 22.214.171.124307141637-r (org.eclipse.egit.ui 126.96.36.199307141637-r) requires ‘bundle org.eclipse.team.core [3.6.100,4.0.0)' but it could not be found". See this forum thread. The solution is to use 'http://download.eclipse.org/egit/updates-2.2/' as update site.
- Use the menu Help > Install New Software and press 'Add...' button
- Specify http://download.eclipse.org/egit/updates as URL. This is the URL which has the latest and greatest eGit version. However, as CodeWarrior for MCU10.4 is using an older version, use http://download.eclipse.org/egit/updates-2.2/
eGit Repository for MCU10.4
Standard eGit Repository Location
- I’m not interested in the sources, so I just select the plugin:
Eclipse EGit Selection
Pressing Next, and it should not report any dependency problems. Go through the rest of the dialogs, and after a restart you have eGit integrated in Eclipse.Summary
Having an Eclipse Git integration as eGit is really nice, and not difficult to install. The only hick-up is if using an older Eclipse version as CodeWarrior for MCU10.4. Then using the dedicated update site http://download.eclipse.org/egit/updates-2.2/ solves the problem.
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)