| Summary: | Ignored Resourced are sometimes displayed in the Team Synchronization view | ||
|---|---|---|---|
| Product: | [Technology] Subversive | Reporter: | mark |
| Component: | UI | Assignee: | Igor Burilo <igor.burilo> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | CC: | a.gurov, achsogehtdas, david.mccabe, jskov, jtk499, remy.suen, vasiliy.gagin, youngm |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
mark
Which version control plug-in are you using, by the way? (In reply to comment #1) > Which version control plug-in are you using, by the way? SVN, with the SVN Kit 1.6 Connector. I should add that often the ignored resources will dissappear when I re-synchronize my entire workspace. However, sometimes I can re-synchronize several times, and the ignore resources will remain present. When that happens, are those resources marked as out-of-sync in the Package Explorer? Or is that limited to the Sync view only? (In reply to comment #4) > When that happens, are those resources marked as out-of-sync in the Package > Explorer? Or is that limited to the Sync view only? It's limited to the Sync view. The files appear with the little question mark icon, as if they were added to the project locally, but have not been committed yet. Mark, are you using Subversive or Subclipse plug-in? (In reply to comment #6) > Mark, are you using Subversive or Subclipse plug-in? Subversive Moving to Subversive for comment then. (In reply to comment #8) > Moving to Subversive for comment then. I see you also moved this to the UI component. I think this might go deeper than UI, since the would be ignored directories actually do get committed if I commit the entire project. This is happening almost every time I synchronize now. Does anyone know of any troubleshooting steps I can take to isolate the problem? (In reply to comment #9) > I see you also moved this to the UI component. I did that arbitrarily, I'm sure guys from Subversive will correct that if needed. (In reply to comment #10) > Does anyone know of any troubleshooting steps I can take to isolate the problem? I guess Igor (or whoever will triage this bug) will ask *you* about that. I'm experiencing the exact same problem with version 0.7.9I20100512-1900 You can somewhat duplicate this problem by: 1. Creating a new file that is not in svn 2. Confirm that the resource has a '?' on it in project view. 3. Check Synchronized View and confirm it is there in outgoing. 4. Add an ignored resource with the exact same name as this new file. 5. Confirm that in the project view the resource no longer has a '?' next to it. 6. Check Synchronized View and confirm it is very hard to make this resource disappear from synchronized view after repeated "Synchronizing", etc. it may disappear though usually I need to restart eclipse. 7. Try removing the "ignored resource" and repeat 5-6 in inverse. The steps above duplicate it for a new ignored resource. Seemingly randomly the IDE will also suddenly forget about any ignored resources it has had since start up and throw everything ignored into synchronized view. These are equally hard to remove but this situation is more difficult to duplication. When I encounter it, this bug seems related to ignoring folders. I use m2e, but due to our classloader I change the output build directory of the projects to point to a linked resource elsewhere. Of course, m2e still generates artifacts in the 'target' folder when doing a Maven build, so I have added 'target' to the Team - Ignored Resources list. It appears that Subversive successfully ignores the 'target' folder, but sometimes does not ignore the contents of that folder. This is not restricted to this use case; I also have folders that are generated inside project folders related to non-Eclipse build tools, and these generated folders are ignored but their contents may not be. The folder that is not correctly processed is not an output folder. This often happens when it resynchronizes after a commit or update. This never happens when doing a brand-new synchronize, so the way to clear the issue (for me) is to click the drop-down arrow next to the Synchronize button and use the Synchronize dialog box to synchronize the workspace. Simply clicking the Synchronize button does not clear the list. These two actions should not give different results, so this is clearly a bug. Subversive never marks the 'ignored' folder as requiring addition - it has no overlay icon at all - but the contents are marked as such. I see the same behavior in Version: Indigo Service Release 2 Build id: 20120216-1857 We also see this problem.
We use Eclipse 3.7sr2 with Subversive 2.2.2.I20120210-1700
This is easiest to reproduce by doing partial commits from the syncronize view:
1. Change a file already under version control.
2. Synchronize the project (Team->Synchronize Project).
3. right-click on the file, select Commit.
4. View is now updated, showing all our ignored resources ('build'+'dist' and all their children).
Alexander, are you aware of this issue? (In reply to comment #17) > Alexander, are you aware of this issue? I haven't seen this behaviour, not even once. Also I wasn't able to reproduce it with the steps provided. So, I do not understand yet what causes such a behaviour. The non-version controlled items that appear in our synchronization view are all custom entries in Preferences->Team->Ignored Resources. And they are all folders (and their content, obviously). Other ignored folderes which are not updated during normal build (i.e. require special action to change) do not appear. I have also seen the ignored folders appeared at once when I synchronize - this happens if a build is occuring/just completing while I synchonize. Hope that helps. I'm having this problem periodically. Had it on Indigo. Upgraded to Juno, still having it. In my case it is with "target" directory. We use maven for build. It is marked for "svn:ignore", command line svn client does ignore it. I do not know how to reproduce it. But may be I can help debug it. If somebody can guide me through. I never debugged Eclipse before. Duplicate *** This bug has been marked as a duplicate of bug 392750 *** |