- This topic has 3 replies, 2 voices, and was last updated 17 years, 1 month ago by
.
-
Posts
-
In order to preserve the ‘web project’ capability, we decided to store the ‘.mymetadata’ file in source control.
However, whenever we check out our project, or close/open our project, this file is being regenerated/modified.
Why can’t it be left alone unless we make changes on the corresponding configuration page? It is very annoying to see this file modified after a fresh checkout.
In order to preserve the ‘web project’ capability, we decided to store the ‘.mymetadata’ file in source control.
If you are maintaining your project within a source management system, e.g., CVS, you HAVE to include the .mymetadata file under version control.
Why can’t it be left alone unless we make changes on the corresponding configuration page? It is very annoying to see this file modified after a fresh checkout.
The .mymetadata file is an XML formatted file that defines MyEclipse-specific information such as the location of the web-root folder and other important details required by MyEclipse web tools for their proper operation. This file is automatically modified and you cannot control it.
I understand all you stated and am well aware of this.
However, everytime this project is checked out of revision control (in our case, Subversion), the .mymetadata file is updated, and then marked as changed.
Why?
This is especially evident if I check out more than one copy of my project, each with a different destination name.
For example, a project named ‘A’, I could check out as a-trunk, a-branch, a-work, etc. I do NOT want any information in the .mymetadata file to change, but it insists on updating after each checkout, and also after any close/open cycle on the project. Is there no way to prevent this?
