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

EGIT: problems using eclipse project below root of working tree

From
John Bito <jwbito@gmail.com>
Date
Apr 29, 2009, 18:28 UTC
Message-ID
<3ae83b000904291128j27ad6c1ah3422f091c956533@mail.gmail.com>

My Java project is part of a larger repository, so the Eclipse project I'm opening is rooted one level below the directory containing .git/.

When I open only the subproject (the root project shows as closed in the project explorer), all the members of the working directory of the subproject show in the Project Explorer as if they were untracked files (query icon). If I open the subproject after opening the root project, the members correctly appear as committed (can icon). Opening the root project after opening the subproject seems to produce an error in references to jars in the subproject - not obviously related to EGIT.

If the root project is open, changes made in the subproject are listed twice in the Commit dialog (once prefixed by root-project-name: and once prefixed by subproject-name:). If the root project is closed, the Commit dialog lists the changes once (prefixed by subproject-name).

I think the commit dialog gives me the correct status, but I'd have more confidence if the icons in the Project Explorer were consistent. I don't want to work with the root project open because it's MUCH bigger than the Java code I'm working on and Eclipse seems faster with only the subproject open. I'm also concerned that if I let it commit with both the root and subproject instances of the changes checked, I'll cause a problem that'll take some time to unwind (not interested in experimenting with that at the moment).

Should I add this as a bug?
Next: Robin Rosenberg
Message 1 of 2 in “EGIT: problems using eclipse project below root of working tree”
  1. John BitoApr 29, 2009
  2. Robin RosenbergApr 30, 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.