| Summary: | Team-View empty after committing only a subset of files | ||
|---|---|---|---|
| Product: | [Technology] Subversive | Reporter: | Konrad Windszus <konrad_w> |
| Component: | UI | Assignee: | Igor Burilo <igor.burilo> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | a.gurov, stefan.home, vkhomyackov |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Mac OS X - Carbon (unsup.) | ||
| Whiteboard: | |||
|
Description
Konrad Windszus
I have tried to reproduce the issue without any success. 1) Could you tell please how exactly do you commit those files? Using selection and the popu-up menu action in the Synchronize View, or the same way in the Navigator or in any other way? 2) Could you please specify Subversive and Subversive Connectors version? 3) Also what is the Eclipse distribution type you are using? (At least for me the issue you have mentioned can't be reproduced in any Eclipse IDE packages related to the Java development, while Eclipse with PDT shows another issue: not all of the committed files are removed from Synchronize View after commit - annoying, but looks like it is related to PDT somehow.) Sorry for being not descriptive enough. Seems to be only a problem if I am in the synchronize view and selected the filter for "Outgoing Mode". If I have more than one item in this view (with the filter applied) and right click on one item, and select commit, the view is empty after that, although the other items should be there still. That does no happen with the filter "Incoming/Outgoing Mode". This is my configuration: - SVNKit 1.3.5 Implementation (Optional) 2.2.2.I20110602-1700 org.polarion.eclipse.team.svn.connector.svnkit16.feature.group Polarion Software - Subversive SVN Connectors 2.2.2.I20110602-1700 org.polarion.eclipse.team.svn.connector.feature.group Polarion Software - Subversive SVN Team Provider (Incubation) 0.7.9.I20110819-1700 org.eclipse.team.svn.feature.group Eclipse.org Sorry I forgot to mention that my Eclipse distribution is 3.7.0 JEE (Indigo) Unfortunately, I can reproduce this each time, I commit, update or merge files, as long I have the Outgoing, Incoming or Confilcts Mode in the synchronize view on. Subversive 0.7.9.I20110602-1700 Native JavaHL 1.6 2.2.2.I20110602-1700 Eclipse 3.7 for Java Developers. Most likely the issue is a duplicate of bug #364599. There is also a possibility of it being related to the bug #230853 *** This bug has been marked as a duplicate of bug 364599 *** (In reply to comment #1) > while Eclipse with PDT > shows another issue: not all of the committed files are removed from > Synchronize View after commit - annoying, but looks like it is related to PDT > somehow. I see this issue from time to time on my Eclipse (Java EE IDE for Web Developers, Version: Indigo Service Release 1, Build id: 20110916-0149, Subversive SVN Connectors 2.2.2.I20110602-1700, SVNKit 1.3.5 Implementation 2.2.2.I20110602-1700, Subversive SVN Team Provider 0.7.9.I20110819-1700, no PDT installed). These committed files disappear after restarting Eclipse or invoking SVN update on project in Navigator View and synchronizing with SVN (Team -> Update, then Team -> Synchronize with Repository). Should a ticket be opened for this issue? (In reply to comment #6) > (In reply to comment #1) > > while Eclipse with PDT > > shows another issue: not all of the committed files are removed from > > Synchronize View after commit - annoying, but looks like it is related to PDT > > somehow. > > I see this issue from time to time on my Eclipse (Java EE IDE for Web > Developers, Version: Indigo Service Release 1, Build id: 20110916-0149, > Subversive SVN Connectors 2.2.2.I20110602-1700, SVNKit 1.3.5 Implementation > 2.2.2.I20110602-1700, Subversive SVN Team Provider 0.7.9.I20110819-1700, no PDT > installed). > > These committed files disappear after restarting Eclipse or invoking SVN update > on project in Navigator View and synchronizing with SVN (Team -> Update, then > Team -> Synchronize with Repository). > > Should a ticket be opened for this issue? This issue should be related to already closed bug #329555. It's just that the build you're using does not have the fix yet, since the build number fo the build with the fix is 0.7.9.I20111123-1700. |