IBM Support

Should the .setting folder for the project be kept under source control?

Troubleshooting


Problem

Are the files in the .settings folder workspace specific? Should those files be kept under the source control system, or should they be left outside of the source control system?

Symptom

The following build errors are reported when a project from the source control system (Rational ClearCase) is checked out:

"One or more required project facets are missing..."

Cause

The .settings folder is for settings that apply to the project. Having all the settings about the project reside in a single folder allows the entire project to be sent to a Source Control Management system like CVS/ClearCase. This enable other users to retain these settings when the project is checked out on their own systems. This folder is not workspace specific, but rather project specific. You should keep it under your source control system if you want every user who checks out the project in another workspace to have the same project settings. This includes the project facets, resource configuration, module source path, and deploy path etc.

Resolving The Problem

To resolve the problem for the missing project facets in WebSphere Integration Developer V7.0.0.3, right click on the error marker, and select "Quick fix" from the context menu. This should add the missing project facets back into the project setting. You can also get a good copy of the .setting folder from the original project workspace, and copy it over to the problematic workspace.

[{"Product":{"code":"SSQQFK","label":"WebSphere Integration Developer"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Team repository","Platform":[{"code":"PF033","label":"Windows"}],"Version":"7.0;7.0.0.3;7.0.0.2;7.0.0.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
15 June 2018

UID

swg21461600