| Summary: | Support filtered resources (they are considered as deleted in Staging view, Commit Dialog) | ||
|---|---|---|---|
| Product: | [Technology] EGit | Reporter: | Alexandre Garnier <zigarn+eclipse> |
| Component: | Core | Assignee: | Robin Stocker <robin> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | CC: | caniszczyk, matthew, matthias.sohn, rainer.frey, remy.suen, robin, tex-hex |
| Version: | 2.2 | Keywords: | noteworthy |
| Target Milestone: | 2.2 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Alexandre Garnier
It is weirder when resources are in other project.
E.g. with this structure :
module
|- pom.xml
`- sub-module
`- pom.xml
With m2e, there is 2 projects 'module' and 'submodule', so to avoid content duplication, I exclude sub-module from 'module' project.
Result:
- all sub-module content is considered as deleted in 'Git Staging' view
- all sub-module content is considered as untracked (with a question mark) in 'Package' and 'Navigator' views and in 'Synchronize' view
Now I got the same problems since I upgraded EGit to Version 2.0. In Version 1.3 everything was fine. The problem is in ContainerTreeIterator, here:
private Entry[] entries() {
final IResource[] all;
try {
all = node.members(IContainer.INCLUDE_HIDDEN);
members doesn't return filtered resources, so later they are reported as missing. I've found no API to get to the filtered resources.
Could anyone with knowledge of org.eclipse.core.resources help out?
*** Bug 384102 has been marked as a duplicate of this bug. *** I looked into this and have pushed a solution to review: https://git.eclipse.org/r/8989 (JGit) https://git.eclipse.org/r/8990 (EGit) It works well with an example nested project structure. There are some possibly surprising things. E.g. when doing "Add to Index" on the root project, the sub projects are also affected. Maybe we need to make "Add to Index" smarter so that it traverses the resources itself and then only adds the resulting files via AddCommand. But that should not block the inclusion of above change. jgit changed fix in master oops, closed the bug w/o the egit changes merged egit change as 0fa1895d31bcbee85e626c578d14b9b17324dd45 |