[egit] Git repository with multiple eclipse projects ?

I am investigating whether it is possible at all to have several eclipse projects in a single git repo, and have those projects correctly seen as managed by git.

When importing a git repo into eclipse, we get a list of projects to import, but that list is empty. What is expected by egit to get this list filled ?

It also does not look like it would be possible to use the "share" functionnality to setup such a repository from multiple projects (or from a project set), right ?

Best regards,

Le mercredi 25 novembre 2009 à 17:47 +0100, Yann Dirson a écrit :

The last time I worked with egit, it was not yet implemented.

Yann

onsdag 25 november 2009 17:47:34 skrev  Yann Dirson:

Both Egit and Jgit themselves have multiple projects in the same repo. All projects must be located in the same directory structure.

repo/.git
    |`--project1/.git
    |`--project2

etc Other variations are possible.

Share only tells Eclipse to attach EGit as the team provider, provided it is located in a git repo, or lets you create a repo if none exists.

-- robin

On Wed, Nov 25, 2009 at 10:27:39PM +0100, Robin Rosenberg wrote:

You seem to talk about nested git repo here. Do you mean using submodules (I thought jgit did not support them yet) ? git-subtree ?

Looks like there is a possibly-windows-specific issue here.

The test repo is a git repo with a couple of eclipse projects just beneath the top-level. It can be checked-out from both Ubuntu (Karmic) and Windows (Vista), and in both cases the projects can be attached to the team provider from the "import" wizard.

On an Ubuntu box, I could use "team/disconnect", and then "share" to attach to "../.git", it worked like a charm. On the windows box however, reconnecting was not possible: the "../.git" line is not selectable. Note that it does read "../.git" and not "..\.git".

Note that on my "mostly squeeze" Debian box, the import would succeed, but in that case none of the projects were attached to the team provider. If afterwards I try to connect it, it silently does nothing.

In that case it may be a known bug: I have a ~/.git dir that is also seen by jgit, and which I am also proposed in the "share" dialog. If I move it away, the request to attach is successful.

Best regards,

Yann Dirson <ydirson@linagora.com> wrote:

As Robin said, it should work.  EGit and JGit both use this layout.
 

There should be .project files in the repository. I think we scan the entire checkout tree for .project files, but maybe we are doing something stupid and only looking at the top level directory of the checkout.

Nope, I don't think this is supported right now. You need to initialize the git repository by hand in the higher level directory that holds the projects.

(worksforme) egit 0.5.x

On Wed, Nov 25, 2009 at 10:48 PM, Shawn O. Pearce <spearce@spearce.org> wrote:

2009/11/26 Shawn O. Pearce <spearce@spearce.org>:

That was the question I initialy understood.

On Wed, Nov 25, 2009 at 04:48:17PM -0800, Shawn O. Pearce wrote:

Right, we could make it work - the devs just did not have the habbit of commiting .project files.

Yes, we did that by git-add'ing the initial projects manually and pushing them, and we can now "import" that.

That makes me wonder if it should work to add a new project afterwards from within Eclipse. If we create a new project under the git tree, and try to use "share", then we get presented a folded list containing the project we want to add, which when unfolded reveals "..\.git" (yes, this test done on windows) as repository, which is promising.

But then the field below near the "Create" button (the one with "\.git" text on the right) gets polulated with the full project path when we click on the project in the list, and we could not unlock the "next" or "finish" button. Are we just trying things the way they should work but hit functionnality that is just not finished, or are we completely off-track ?

Thanks much,