Bug 401869

Summary:	Compare-Resources-View should allow to Compare filtererd Resources
Product:	[Eclipse Project] Platform	Reporter:	Peter <p.rader>
Component:	Resources	Assignee:	Platform-Resources-Inbox <platform-resources-inbox>
Status:	NEW ---	QA Contact:
Severity:	enhancement
Priority:	P3
Version:	4.3
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description Peter

2013-02-27 05:21:28 EST

Well, this is a very localized problem.

I have nested Java/Maven multi-projects structure for example. 

+- Pizzashop Trunk (Maven)
   +- Frontend (Maven, Javascript)
   +- Backend (Maven, Java)

In Eclipse i use 3 Projects for Trunk (Pizzashop as plain Project, Pizzashop/Frontend as Javascript-Project and Pizzashop/Backend as Java-Project). 

Ok, if i search for a Resource, Eclipse always found duplicate files then (occourences in Pizzashop/Frontend and Frontend). 

To filter duplicated Resources in the search-view, i filter the resource-folders "Frontend" and "Backend" in Pizzashop (i filter the target-folders also).

Now, i got the Release-Branch of "Pizzashop"

+- Pizzashop Release (Maven)
   +- Frontend (Maven, Javascript)
   +- Backend (Maven, Java)

If i compare the projects "Pizzashop Trunk" and "Pizzashop Release", i see only the pom.xml-differences because of all other resources are filtered.

Can you please add a checkbox in the Folder-Comparisation-View that ignores the resource-filters?

Or can we define a new type of Resource-Filters who are only attached to the search-view?

Regards.

Comment 1 Lars Vogel

2019-11-27 07:12:53 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.