On Jan 5, 2008, at 2:26 PM, Daniel S. Haischt wrote:
wouldn't it be possible to just remove the keyword temporarily and let
Mohammad re-try whether the issue still persists? That way you would
be
more or less certain that it's related to the SVN keyword and thus
removing them is a legit approach.
Mohammad, can you give that a try? You should be able to just delete
the svn keywords section on your local copy and build.
As a side note: encoding="UTF-8" doesn't mean that the file is UTF-8
encoded per se (i.e. the user explicitly specified in notepad to save
the file as UTF-8 ensures that the file is being saved as UTF-8
encoded
to the file system). That's something I tried to point out earlier.
Yes, that's exactly what I said. I just don't think it's Eclipse
doing it which is what I tried to point out. Seems more likely that
it's his svn client.
-David
David Blevins wrote:
On Jan 5, 2008, at 8:14 AM, Jacek Laskowski wrote:
On Jan 5, 2008 1:20 PM, Daniel S. Haischt <[EMAIL PROTECTED]
> wrote:
Again I think this is a pure Eclipse issue if not reported
different
by someone else who tries to open the files in IntelliJ for example
and experiences the same exact issue.
I'm working with Eclipse, NetBeans and IntelliJ recently and none's
reported troubles opening the files so I think you're right. Thanks
Daniel for the report as I wouldn't figure that out myself.
I don't think it's it. The user complained that his *maven* build
failed and that he had non-UTF8 characters in the part where svn
substitutes the keywords. The xml files clearly state
encoding="UTF-8" and his svn client is adding non-UTF8 characters
when it edits the file while adding the keywords making it
unparsable, I'd guess, by any valid xml parser who listens to the
'encoding' attribute.
Regardless, even if we can explain it that doesn't make it gone, it
still needs to be fixed. The only fix I see is to yank the
keywords if svn is going mix character encodings on us. Could be
just TortiseSVN, but still.
Any other thoughts or proposed solutions?
-David
