Re: [egit-dev] Trying to convince Kepler to see a clone of a remote

["Randall S. Becker" <rsbecker@xxxxxxxxxxxxx>]

Unfortunately, the use of Kepler is not my call. There is a product plug-in that has a version dependency that limits to Kepler only. To be fair, I did try the Auto-Share option (on by default) with no success on that. This seems only to be a factor on the initial clone anyway, specifically on RepositoryUtil#addConfiguredRepository(File).

 

Is there a reason on the restricted access for egit.core (as opposed to egit.internal)?

 

From: Matthias Sohn [mailto:matthias.sohn@xxxxxxxxx]
Sent: August 12, 2015 4:58 PM
To: Randall S. Becker <rsbecker@xxxxxxxxxxxxx>
Cc: EGit developer discussion <egit-dev@xxxxxxxxxxx>
Subject: Re: [egit-dev] Trying to convince Kepler to see a clone of a remote

 

On Mon, Aug 10, 2015 at 10:21 PM, Randall S. Becker <rsbecker@xxxxxxxxxxxxx> wrote:

G’day,

 

I have what should be a simple question.

 

Given a remote repo, with SSH auth (not really relevant).

Attempting to clone the remote to a local drive under windows with ECLIPSE Kepler RC2.

 

why are you using a release candidate of an Eclipse version from 2013 ?

 

If you are using a recent version of EGit and auto-sharing projects is switched on

under "Preferences > Team > Git > Projects" it should be sufficient to import any project

contained in a git repository to make EGit aware of this git repository and it should show up in

the repositories view and show the usual decorators in project explorer and similar views

like Java package explorer

 

-Matthias