Hi, Greg,

In general, nothing from the workspace's .metadata folder is expected to be managed in source control.  The vast 
majority of the data in there comprises four categories of volatile and user-specific information:

  - record of which projects are instantiated in the workspace
    and where on the filesystem its resources are stored
  - caches of computed information, such as the build state
    of projects, indexes for fast searching, etc.
  - user preferences for layout of the user interface, records
    of user input into dialogs and wizards, and other options
  - logging/diagnostic information

Anything from the workspace folder that you might want to share with a team usually provides a better way than sharing 
the workspace metadata:

  - project-set files (*.psf) provide a means to share with a
    team a set of projects with the SVN URLs from which
    they are checked out
  - preferences such as common toolchain/compiler settings,
    code templates, and the like can be shared via export to
    *.epf files.  Although, most preferences can also be
    maintained within the projects, which are already shared
    in SVN

HTH,

Christian


On 2011-05-16, at 4:41 AM, Gregoire Banderet wrote:

> Hello,
> 
> We are using Momentics (Eclipse / CDT) for our C/C++ projects, and Subversion as source control system.
> 
> We checked-in .cproject and .project files into SVN.
> And we are wondering which fiels from the .metadata folder we should also check-in?
> Some files contain absolute paths to the workspace, and all the developer do not have the same directory structure...
> So what the common way to work with Momentics and source control?
> 
> Thanks,
> Greg
> 
> 
> 
> _______________________________________________
> 
> QNX Momentics Community Support
> http://community.qnx.com/sf/go/post85698
> 

----
Christian W. Damus
Software Developer, IDE Team
QNX Software Systems <http://www.qnx.com/>;