Skip to main content

Resolve 'Detecting library folders' error in Eclipse

Eclipse maintains a directory at the root of a project with the name ".settings."  If, for whatever reason, Eclipse can't seem to find this directory, or the files in it, Eclipse will report an error vaguely stating a problem "Detecting library folders."  Removing the .settings directory will solve the problem.

Presumably, Eclipse rebuilds any information it maintains in that directory, though it's not clear what the information is.  Assume that any arbitrary details that seem off might be associated with removing this folder.


The "Detecting library folders" error dialogue window.

Due to the non sequitur nature of the error, there isn't much context to work off of other than the "org.eclipse.wst.validation" identifier, and the "detecting library folders" pseudo-clue.  As such, there isn't much that comes back from searches around the web for solutions to the issue, but the combination of the three references below "did the trick."  While not perfectly describing the issue, they did lead to the solution.

NOTE:  The Stack Overflow article specifically mentions Zend Studio instead of Eclipse.
NOTE:  The second resource, is from a Chinese site and mentions the issue as it relates to Mylyn, but the solution to the error for Mylyn was the same as for Eclipse.  UPDATED 02/02/2017:  This resource appears to be the victim of link rot, but will remain for the time being for the sake of citation.
NOTE:  The third item is also from Stack Overflow.  From what can be gleaned from the second resource, this resource is the inspiration of the solution described in the second one.


Resources

Error “Detecting Library Folders” in Zend Studio
http://stackoverflow.com/questions/25947959/error-detecting-library-folders-in-zend-studio

"org.eclipse.wst.validation" has been removed
http://www.csdn123.com/html/topnews201408/65/13065.htm
(Link appears to be dead.)

updating maven project has encountred
http://stackoverflow.com/questions/21414565/updating-maven-project-has-encountred

If hunting for reasons why this situation may arise, at the very least, moving projects around as described in another article may do it.  See "Migrating Eclipse projects to new locations" for more.
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