[Keith Fetterman]

When MyEclipse 4.0.3 creates or updates the .mymetadata file, it uses CRLF line ending characters on a Linux platform. Shouldn’t it be using the LF line ending character since it is a text file?

This creates havoc with CVS since CVS expects ASCII files to have LF characters when checked in from a Linux/UNIX system.

I think this is a bug. Or, I could treat these files as binary files in CVS. What is your expectation on how these files should be handled on Linux/UNIX and CVS?

Thanks,
Keith

[Scott Anderson]

Keith,

They should be treated as ASCII and I’ll enter this as a bug. The workaround would be to treat them as binary in the interim if they’re problematic.

[Keith Fetterman]

Thanks. It is a pain when you have some developers on windows and some on linux.

[_bjoern]

We use Eclipse 3.1.1, with MyEclipse 4.0.3.
We have similar and various other bugs related to the .mymetadata file

Sometimes the file is gone at all…. deleted.
Sometimes the file is saved with the errors above… additionally the file
content changes, for example the j2ee spec defined in the file changes from 1.3 to 1.4

Our Versioning System stores the .mymetadata file with write protection.
Sometimes MyEclipse does even change the write protected .mymetadata file.

[Author]

Posts