Myeclipse/eclipse git plugin installation tutorial

MyEclipse git plug-in installation use

Installation Instructions

1. For the introduction and use of Git please refer to other articles, this article just specifically said myeclipse+git use
2. Because of the use of myeclipse+git, you do not need to install GIT clients and graphics programs, only one Egit plug-in
3. Same applies to Eclipse+git

Installing the Egit Plugin

1. Method One:
Download the Egit package and then install the Egit plugin via dropins+link or otherwise
2. Method Two:
MyEclipse help?eclipse Marketplace?search Egit?finish
3. Method Three:
MyEclipse myeclipse configuration center?software? installation

Using Git

1. Create a new project
2. Right key to this project? team?share project?git check box? Click item? Create Repository?finish
The 3.git warehouse has been built and can be versioned locally.

Remote Git

1. You can apply for an account in Code.csdn, Git.oschina, or other foreign code management sites, and then use remote git
2. Right key item? Team?remote?push? Fill in the relevant information? finish

Eclipse Plug-in Egit installation use

Installation of 1.egit

Of course, you can also choose to search in Eclipse marketplace

Experienced friends will certainly think that it is not possible to use link to implement plug-in installation, as if this really did not

Another explanation is that if you use: http://download.eclipse.org/egit/updates to install, make sure your eclipse version is up to date, or it will fail to install.

Low version eclipse install Egit plugin

My eclipse is in the 3.6 version, just can't use the way described above, the processing method is as follows

Open Http://wiki.eclipse.org/EGit/FAQ#Where_can_I_find_older_releases_of_EGit.3F

Select http://download.eclipse.org/egit/updates-1.3 (because this version of the release time is similar to the Eclipse3.6 release time, the other version of the same try)

Next in the end is OK.

Second, configure Egit

The premise here is that there must be a GIT client installed on the computer first.

Installation Address: Http://code.google.com/p/msysgit/downloads/list?q=full+installer+official+git

After installation, open eclipse

Select the repository path for the GIT client, then configure user settings user and email in configuration

This username must be GitHub user, not yet registered, click here to apply for https://github.com/

To this end, the configuration of the plug-in ends

Very excited to start creating a demo try

File > Team > Share Project Select git

When you check git here, you will be prompted to set the home environment variable

Hom-->%userprofile%

Then you create a warehouse

Third, upload the project

First you need to login GitHub

Create an empty warehouse

Click Create a new repository

Since I have created a gitdemo, I will not demonstrate

Click Upload

Tip exception caught during execution of ls-remote command

Found that there is no private key.

Here is a brief description of how the Egit works

In fact, a friend who is familiar with CVS or SVN must know that when we click on a commit, the version manager will update the content we modified

But Egit is not so smart, in fact, Git has a concept of a local warehouse, which means that when we commit, we put the updated content information

Sync to the local warehouse, and click Push to submit the updates in the local warehouse to GitHub

Local warehouse path Window-->show view-->other-->git repositories

Say more, I do not know if you have no impression, the first configuration of the user settings egit after the name, no password

passwords aren ' t very secure, you already know this. If use one of that ' s easy to remember, it's easier to guess or brute-force (try many options until one works). If use one of that ' s random it's hard to remember, and thus you ' re more inclined to write the password down. Both of are Very bad things™. This is why for you using the SSH keys.

afore-mentioned this paragraph is the explanation that GitHub gives, popular Point says, GitHub worry the user uses too simple password to cause security hidden trouble, or the password is too complex cause the user is difficult to remember bring not need to bother

So using the SSH keys way

IV. SSH configuration

How to generate your own SSH Kyes, which operates as follows

1. Open git Bash

Enter Ssh-t git@github.com

Found no RSA file

then enter

# ssh-t Git@github.com

Hint does not have permissions.

Continue Typing

Ssh-keygen (Always enter)

The above path is not unique, and everyone is holding on to the path of the home configuration before

The final Test

Configure SSH2

Simply explained, previously uploaded is the SSH keys of the public key, and Id_rsa is stored in our private key, so when we upload (push) only need

Enter a public account git can

As an example

After submitting, is push

The UI here is the warehouse address we created earlier in GitHub.

Niext, click Finish to complete the push to the server operation

To this end, the Egit installation configuration ends