[dbaldes]

Hello there,

we have a problem with some project specific settings not being stored in CVS:

In project properties -> MyEclipse Web -> Deployment we use project specific settings
(o) Use smart deployment for dependent Java Projects and
[x] Jars exported by dependent Java Projects

Wenn we commit the Project to CVS and check it out elsewhere, these settings are lost ([x] Use Workbench default settings is checked again).

Additionally, every time we check out the project, eclipse immediately displays a change (“>” before the project name), and on “commit” it displays the file .mymetadata as changed. We checked the file with a text editor and cannot see any changes. When we commit this file and check it out again, it still says it would be revision 1.1. cvs complains about CR/LF linefeeds in some files, including .mymetadata, in <workspace>/.metadata/.log, but other files with this problem get saved, committed and checked out correctly.

Now one could think “this must be the file where those settings are stored”, but it doesn’t look like it, and after changing the settings, the file does not change.

thanks in advance for your help!

—
System details according to the posting guidelines:

OS: Linux 2.6.11.12-6trsmp
Eclipse 3.1.1, Build id M20050929-0840
– Eclipse was freshly installed
(-> it was not updated using the update manager)
– One other plugin installed: Kodo plugin for Eclipse
– 7 plugins are like org.eclipse.pde.*
MyEclipse version: 4.0.0.
java version is 1.4.2_09 (both for eclipse and the application servers)
There are no exceptions in the logfile, but cvs messages as described above

[Riyad Kalla]

The deployment settings are currently stored in the workspace, there is an open enhancement to move them to the project settings. I will add your vote to the bug.

[dbaldes]

Thanks for the quick reply. We are looking forward to this enhancement.

What about the mysterious change of .mymetadata after checking out the project?

thanks in advance!

[Riyad Kalla]

What about the mysterious change of .mymetadata after checking out the project?

I think this is just an unnecessary re-generation step that is occuring on our end that is re-creating the exact same file. I’ll ask someone to look into it.

[Author]

Posts