EGIT: problems using eclipse project below root of working tree

EGIT: problems using eclipse project below root of working tree

[John Bito]

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?

Re: EGIT: problems using eclipse project below root of working tree

[Robin Rosenberg]

onsdag 29 april 2009 20:28:22 skrev John Bito <jwbito@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?

We had such a bug, fixed in february, I think, but we now have projects at 
this and and other levels. If you are talking 1) nested repos or 2) nested projects, 
then 1) Egit doesn't work well with them and 2) Eclipse doesn't work well with them.

We have been fiddling around recently with bugs relating to what happends in the repo
after fetch. Those would result in lost decorations. If you have an "exact" receipe for
reproducing the failure, a bug report helps. Otherwise we know there is some work
to do related to nested repos and odd setups in general.

-- robin