Bugzilla – Full Text Bug Listing
| Summary: | [plan item] Improve local history | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Jim des Rivieres <jeem> |
| Component: | Resources | Assignee: | DJ Houghton <dj.houghton> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P4 | CC: | eclipse, ekuleshov, jed.anderson, veronika_irvine |
| Version: | 2.1 | Keywords: | plan |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Jim des Rivieres
*** Bug 40660 has been marked as a duplicate of this bug. *** From bug 40660: When debugging a problem involving an interaction between my plugin and eclipse (which happens every time there is a bug in eclipse that we can not reproduce with a standalone SWT example - i.e. a lot) I will import all of Eclipse into my workspace as "Projects with Source folders" and then start hacking - both in SWT and in other plugins. The problem is that from time to time, I would like to see just exactly what I have hacked. Since I am not connected to a repository, there is no indication of what projects or classes have been modified and no general way to do a comparison against the base (what I imported). I think this is a pretty common scenario for people developing a sub-part of a large project. Without the ability to quickly see what has been modified, the ability to import existing plugins as source is significantly reduced in usefulness. I would like to see some improvements of the local history: - allow set "landmakrs" in the local history (points with a name in the history) - landmarks should be applicable to resource, folders (recursively) or (sets of) projects. - allow to see the history of an entire project similar to the CVS synchronize view. But here I wold either use a 'landmark' or specify some timestamp to which I want to compare (and merge!) Why would I want this? Because I don't want to check in unstable versions of my project. However, in development I sometimes know, this is a good state and I maybe want to get back to this state. OK, I can copy the project to a save place, but the I would have to use an external tool to merge. I could also use branching, but I don't want to cast my local explorations into the CMS system.... Hmm, is there a way to "merge" with another snapshot of a project/workspace? The 'landmarks' I proposed above is a bit like creating a snapshot of the workspace and recover to that snapshot with the possibility of merging. Using timestamps is effectively like creating a snapshot on each save.... *** Bug 48413 has been marked as a duplicate of this bug. *** If anyone is working on this plan item please see the new 3.0 Team APIs which will allow local history to be integrated into the synchronize view. Deferred from 3.0 plan From comments to Bug 48413 When CVS update is executed files are updated, however if you are working offline you can't track these changes by using local history. It would be conveneient to see revision in the local history for each updated file, perhaps with the comments from version control. Anyway, is there are any plans to address this in 3.2? [LATER->WONTFIX] The "LATER" bugzilla resolution is being removed so reopening to mark as WONTFIX. [LATER->WONTFIX] The "LATER" bugzilla resolution is being removed so reopening to mark as WONTFIX. |