Eclipse has the ability to prevent certain files from being incorporated into projects or from being scanned during file searches. The limits are applied by way of patterns in the file names.
It may well be the case that several IDEs are used in the development of projects which will litter the projects' folders with IDE support files. These can get in the way of Eclipse, but can be ignored with this resource limiting provision.
To get there:
Some common "exclude" filters might be:
Adding these filters to an Eclipse project should allow the placement of project files for Komodo and Sublime Text without "cluttering-up" the file listings in Eclipse with these project files.
Naturally, this can be translated, or expanded, to apply to whatever external software might be necessary as well. For instance, if Subversion is the source control of choice, then the git exclusion would be ".svn" instead.
It should also be noted that this same technique can be applied to incorporated files into a project as well as opposed to preventing them from being incorporated.
It may well be the case that several IDEs are used in the development of projects which will litter the projects' folders with IDE support files. These can get in the way of Eclipse, but can be ignored with this resource limiting provision.
To get there:
- Right click on a project
- Choose Properties
- Expand Resource
- Choose Resource Filters
Some common "exclude" filters might be:
- .buildpath (file-level should be fine)
- .git (folder-level, and should exclude children as well)
- *.komodoproject (file-level should be fine)
- .project (folder-level, and should exclude children as well)
- .settings (folder-level, and should exclude children as well)
- *.sublime-* (file-level should be fine)
Adding these filters to an Eclipse project should allow the placement of project files for Komodo and Sublime Text without "cluttering-up" the file listings in Eclipse with these project files.
Naturally, this can be translated, or expanded, to apply to whatever external software might be necessary as well. For instance, if Subversion is the source control of choice, then the git exclusion would be ".svn" instead.
It should also be noted that this same technique can be applied to incorporated files into a project as well as opposed to preventing them from being incorporated.
Comments
Post a Comment