Community
Participate
Working Groups
Please check product and component setting... The *global* preference Team->Ignored Resources allows only a global filtering of resources. It could be helpful if each project has the *option* to redefine the Ignored Resources (=project specific settings). Either add additional filters (easy) or disable global filters (difficult). Use cases: Mixed plugin projects with third party files in general, plug-ins using JNI to interface with native dlls, license plug-ins with many binary data and executables. Generally ignored resources, e.g.: *.o, *.dll, *.exe A license plug-in may contain third party dlls that must be delivered by the plugin in the directory my.license.plugin/os/win32/x86 and are ignored by the global filter. Relaxing the filtering will mark too many files in other plug-in projects or annoy other team members...
This makes sense. However, we don't have the manpower to address this in 3.3.
I could lend a hand if you point me to the right starting point... Maybe I return with something useable.
If you wanted to have project specific settings, you would need to do the following: 1) Create an Ignored Resources project properties page that was similar to the IgnorePreferencePage in the org.eclipse.team.ui plugin. The properties page should be simialr to the Java compiler properties page that allow you to either use the global settings or create project specific ones. The Java properties pages are found in the org.eclipse.jdt.ui plugin. 2) Modify the Team#isIgnoredHint method to consult project specific settings.
