Skip to main content

Filters to add to Eclipse projects

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:
  1. Right click on a project
  2. Choose Properties
  3. Expand Resource
  4. 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.
Labels:

Comments

Post a Comment

Popular posts from this blog

Remove control of Chrome being managed by organization on personal devices

Chrome may indicate that it's being managed by a user's organization. This warning is provided by the Chrome Policies feature of the browser. To know if an instance of Chrome is managed by an organization, there will be an entry at the bottom of the browser’s hamburger menu (three dot menu), on the right side of the browser window that reads, "Managed by your organization." This is likely due to an entry in the Chrome Policies listing, which can be found by loading this page in the browser: chrome://policy The policies listed in this section are stored in the computer's file system in one of the following locations as JSON files. /usr/share/chromium/policies/managed /usr/share/chromium/policies/recommended Remove the offending JSON files, and click the Reload policies button. The Managed by your organization entry in the browser menu should be gone. A notice like this on instances of Chrome for work, school, library, or other devices that belong to an organizati...
Post a Comment
Read more

Allow Windows authentication using SQL Server driver with DBeaver

DBeaver will allow Microsoft Windows single sign on access when connecting to Microsoft SQL Server using the SQL Server driver (rather than jTDS ).  From the driver properties settings, set the integratedSecurity flag to true . Open the Connection configuration panel and choose the Driver properties section. Set the integratedSecurity flag to true . A subtle, but important step is to not provide username and password credentials to the connection.
7 comments
Read more

Connecting to SQL Server with jTDS using Windows Authentication

UPDATE:   At one point the tip in this article to set the USENTLV2 flag to true was accurate, but it appears it is no longer necessary, at least as far as DBeaver 's use of the driver is concerned.  If it solves an authentication problem, then great.  The expectation is that, an update in one of the packages that make this sort of connection possible has resolved the issue that at one time made this flag necessary. Connecting to Microsoft SQL Server using jTDS with a username and password that's managed by the database manager is pretty straightforward.  It may become a little more problematic however, when trying to use Windows authentication when connecting from a Windows machine. Do not supply a username and password. Set the USENTLMV2 property to true. NOTE:   Step 1 assumes a connection being made from a Windows machine.  If the connection is being made from something else, user credentials may actually be necessary. If the connect...
7 comments
Read more