| Summary: | [UI] Switching branch in CDOSessionView does not work | ||
|---|---|---|---|
| Product: | [Modeling] EMF | Reporter: | Martin Fluegge <martin.fluegge> |
| Component: | cdo.ui | Assignee: | Eike Stepper <stepper> |
| Status: | ASSIGNED --- | QA Contact: | Eike Stepper <stepper> |
| Severity: | normal | ||
| Priority: | P3 | CC: | extispex, vroldanbet |
| Version: | 4.13 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 337125 | ||
|
Description
Martin Fluegge
I also encountered this bug and "hot"fixed it in org.eclipse.emf.internal.cdo.view.CDOViewImpl.setBranchPoint(CDOBranchPoint branchPoint)
Obviously, the call of getInvalidObjects(timeStamp) results in an empty list, although some (or all) resources should get invalidated.
So I replaced this line:
List<InternalCDOObject> invalidObjects = getInvalidObjects(timeStamp);
by this one:
List<InternalCDOObject> invalidObjects = Arrays.asList(getObjectsArray());
- brute force, I know. But for test&play purposes it works (and I did not encounter any negative side effects up to now).
Committed revision 7064 Committed revision 7067: - trunk/plugins/org.eclipse.emf.cdo.common - trunk/plugins/org.eclipse.emf.cdo.ui - trunk/plugins/org.eclipse.emf.cdo.ui.ide - trunk/plugins/org.eclipse.emf.cdo.ui.location - trunk/plugins/org.eclipse.emf.cdo.ui.shared - trunk/plugins/org.eclipse.net4j.util.ui Committed revision 7068: - trunk/plugins/org.eclipse.emf.cdo - trunk/plugins/org.eclipse.emf.cdo.common - trunk/plugins/org.eclipse.emf.cdo.tests - trunk/plugins/org.eclipse.emf.cdo.ui - trunk/plugins/org.eclipse.emf.cdo.ui.efs - trunk/plugins/org.eclipse.net4j.ui - trunk/plugins/org.eclipse.net4j.util - trunk/plugins/org.eclipse.net4j.util.ui Vik, do you want to check the new UI elements for branching? Just update your workspace... Committed revision 7069: - trunk/plugins/org.eclipse.emf.cdo.ui Committed revision 7072 (test cosmetics) Committed revision 7076 Moving all open bug reports to 4.1 because the release is very near and it's hghly unlikely that there will be spare time to address 4.0 problems. Please make sure that your patches can be applied against the master branch and that your problem is not already fixed there!!! Moving all open issues to 4.2. Open bugs can be ported to 4.1 maintenance after they've been fixed in master. We'll try to address open problems in 4.3 (master) first and then port fixes back to 4.2. Moving all open bugzillas to 4.5. Moving all unaddressed bugzillas to 4.6. Moving all open bugs to 4.7 Moving all unresolved issues to version 4.8- Moving all unresolved issues to version 4.9 Moving to 4.13. |