git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [egit] Git repository with multiple eclipse projects ?

From
Shawn O. Pearce <spearce@spearce.org>
Date
Nov 26, 2009, 00:48 UTC
Message-ID
<20091126004817.GL11919@spearce.org>
In-Reply-To
<20091125164734.GF21347@linagora.com>
Yann Dirson <ydirson@linagora.com> wrote:
> 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.
As Robin said, it should work.  EGit and JGit both use this layout.
 
> 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 ?

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.

> 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 ?

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.

-- 
Shawn.
Previous: Yann DirsonNext: Douglas Campos
Message 5 of 8 in “[egit] Git repository with multiple eclipse projects ?”
  1. Yann DirsonNov 25, 2009
  2. Yann SimonNov 25, 2009
  3. Robin RosenbergNov 25, 2009
  4. Yann DirsonDec 2, 2009
  5. Shawn O. PearceNov 26, 2009
  6. Douglas CamposNov 26, 2009
  7. Yann SimonNov 26, 2009
  8. Yann DirsonNov 26, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.