Community
Participate
Working Groups
When using either CVS or SVN (by means of Subclipse), it is possible to compare a project tree with a branch in the repository (remote/local & remote/remote). The result is a Compare view listing the changed files. Currently it is not possible to print or save the results from this view. Currently the only way of getting the results into another application is by means of screen capture. This feature request would be to allow the results to be saved and/or printed. The saved version could either be a plain text file (not a udiff) or a CSV file. This feature would be useful for anyone wanting to compile a report, or forward information to a deployment team, for example. Note: I have opened ticket 733 in the Subclipe project, which would depend on this feature being provided in Eclipse.
What kind of information would you like to have in this kind of report? IMO a patch file is a perfect solution for a plain text file, but I do understand it can be too detailed in some cases and hard to read. Parsing a patch file, removing the extra information and re-composing it seems to be the easiest solution here. Two ways of doing it come to my mind: an export wizard or a context menu action. On the other hand, we could try to generate the report directly from the sync view, but I don't like the idea personally. As for the graphical representation of the sync I don't think I can offer anything better than a screen capture of the Sync view itself. Any suggestion? How does it sound? A patch would be welcomed and as always I'm eager to help.
For printing: In the most basic form I would have the tree printed as it is displayed. This would provide the simplest and most immediate solution - at least I imagine so, since I haven't looked into the code. The goal of this is to be able to provide a report (printed or saved) of changed files, without necessarily having a list of the specific content changes. In the case of the save report, it could then be imported into a word-processor document or sent by e-mail. I find that I need to do this to let our deployment team know which files to deploy in integration (we only deploy changed files). I imagine that the most suitable format for this report would be a tab delimited text file (though other formats could be possible), that would have the following fields: path of file changed, add/deleted/modified, latest comment. An export wizard could certainly be a solution. What is important here is to make it useful and easy to use. What is developed here could eventually be reused by other source control solutions for Eclipse, such as Subclipse.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
