Bug 367112

Description Steve Ash 2011-12-19 12:50:24 EST

Build Identifier: 20110916-0149

On eclipse 3.7.1 running on opensuse with egit 1.1.0.201109151100-r I experience strange behavior.  Here's the scenario:

I used egit to clone a remote repo that is using HTTP.  The repo structure is like:

/.git
/pom.xml
/project-module-1
/project-module-2

I.e. a typical maven multi-module project.

I do _not_ use the m2e-git connector to import the projects (maybe thats the problem, but I was experiencing other problems with that).  So I do the following:

1) clone in the git repo explorer
2) right click on working directory and import projects
-- this imports the single parent project
3) go to java perspective, and right click on parent to import existing maven projects
-- this brings in the maven submodules as eclipse projects.

Now at this point only the parent project has options under "team".  The submodules don't seem to know they are under egit control.

Then if I modify a file in the submodule projects, it _will_ show up in the git staging view as an unstaged change, but when I right click I do not have an "add to index" option to stage the change.

If I just commit on the parent project, then the modified file shows up and I can "check" it, which is how I'm working.  So I'm not sure if the multi-module aspect is the problem or what.  At home with github, I don't seem to have a problem.  Why would the add to index ever be greyed out for files in the unstaged column?

Reproducible: Always