Bug 152711 - [Structure Compare] Provide compare editor for any zip based files, not just .zip and .jar
Summary: [Structure Compare] Provide compare editor for any zip based files, not just ...
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Compare (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 enhancement with 3 votes (vote)
Target Milestone: ---   Edit
Assignee: Platform-Compare-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 109492 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-08-03 04:39 EDT by Jörg von Frantzius CLA
Modified: 2019-09-06 16:19 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jörg von Frantzius CLA 2006-08-03 04:39:08 EDT 
When comparing two .jar files, the Compare editor nicely shows the differing files and their respective differences when selected. It would be nice if this feature would extend to any zip based files, e.g. OpenOffice *.odt files. 

It would then at least be possible to glean textual changes from the differences in the XML.
Comment 1 Michael Valenta CLA 2006-08-10 14:30:49 EDT 
I agree that this would be helpful. The problem is that the Compare plugin currently depends on structure creators (i.e. the interpretors of the file format) being declared by plugins (i.e. the Java plugins contribute the JAR structure creator). Allowing the user to pick the type would be a fair amount of work. I do't think we'll have time to look at it in 3.3.
Comment 2 Markus Keller CLA 2007-06-11 10:25:38 EDT 
*** Bug 109492 has been marked as a duplicate of this bug. ***
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:19:25 EDT 
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.