Bug 248827

Summary: Compare Editor: Option to ignore changes in comments
Product: [Eclipse Project] Platform Reporter: Axel Mueller <axel.carl.mueller>
Component: CompareAssignee: Platform-Compare-Inbox <platform-compare-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: enhancement    
Priority: P3 CC: cyril.chaize, tomasz.zarna
Version: 3.5   
Target Milestone: ---   
Hardware: PC   
OS: All   
Whiteboard: stalebug

Description Axel Mueller CLA 2008-09-27 06:03:10 EDT
It would be nice to have an option to ignore changes made in comments (like the option "ignore whitespace"). 

The file type should be honoured (different comment signs for Java, C, C++, Perl, etc.).
Comment 1 Tomasz Zarna CLA 2008-09-30 09:50:00 EDT
This sounds reasonable, but to make it available for different source file types every contentMergeViewer[1] provider would have to add this feature to his viewer. The other thing is that in some cases changing comment might be important (take javadocs of API methods for example) and ignoring the change might be risky. Anyway, we could try to implement such a filter for JavaMergeViewer[2] and see how useful it is. Patches will be accepted, feel free to provide one Axel and you need any help let me know.

[1] org.eclipse.compare.contentMergeViewers extension point from org.eclipse.compare
[2] org.eclipse.jdt.internal.ui.compare.JavaMergeViewer from org.eclipse.jdt.ui
Comment 2 Tomasz Zarna CLA 2008-09-30 09:51:02 EDT
Take a look at bug 188050 and bug 15903.
Comment 3 Lars Vogel CLA 2019-11-27 07:07:49 EST
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.

If the bug is still relevant, please remove the stalebug whiteboard tag.