| annoying timestamp change in pref file [message #250341] |
Sat, 22 December 2007 14:44  |
Eclipse User |
|
|
|
Hi
Ever since I activate an APT tool which generates a file (in
bin/META-INF/entities.list,) there is a setting file
or.eclipse.core.resources.prefs being created under .setting.
The problem is that is file always as a timestamp as the first line and
this timestamp always get updated by anyone running a build (and so the
APT tool).
The problem is that I believe this file is used to set the encoding for
specific files in the project, and so it should be under version control
as we will have some encoding specific file. But as the timestamp keeps
changing, there will be merge conflict every time SVN is updated.
Any way to solve this? Why is there a need for this timestamp at all?
#Sat Dec 22 10:27:57 PST 2007 <-- the annoying timestamp
eclipse.preferences.version=1
encoding//bin/META-INF/entities.list=utf-8
instance/org.eclipse.core.net/org.eclipse.core.net.hasMigrat ed=true
|
|
|
| Re: annoying timestamp change in pref file [message #250356 is a reply to message #250341] |
Wed, 26 December 2007 16:19  |
| Eclipse User |
|
|
|
Originally posted by: wharley.bea.com
"hackingbear" <cutebear103@hotmail.com> wrote in message
news:0353066750aeebf640c34b91b2bdff0b$1@www.eclipse.org...
> Hi
>
> Ever since I activate an APT tool which generates a file (in
> bin/META-INF/entities.list,) there is a setting file
> or.eclipse.core.resources.prefs being created under .setting.
>
> The problem is that is file always as a timestamp as the first line and
> this timestamp always get updated by anyone running a build (and so the
> APT tool).
> The problem is that I believe this file is used to set the encoding for
> specific files in the project, and so it should be under version control
> as we will have some encoding specific file. But as the timestamp keeps
> changing, there will be merge conflict every time SVN is updated.
> Any way to solve this? Why is there a need for this timestamp at all?
Yes, isn't that annoying? The basic problem is that Eclipse stores
character encoding preferences for files in that settings file, and that it
includes encodings for derived (generated) files. Derived file information
shouldn't be kept within the project, for exactly the reason you describe.
You can help by voting for
https://bugs.eclipse.org/bugs/show_bug.cgi?id=207510 .
|
|
|
Powered by
FUDForum. Page generated in 0.03680 seconds
Home