Roger Ye wrote:
we can survive if we explicitly set the source file encoding in the
project
pom.xml
Yes, this is right, explicitly setting the encoding is the golden answer.
But will you do so right from the beginning if your platform default
encoding happens to build as you expect or will you just wait until somebody
reports a problem with the build because his default encoding does not work?
the context of this statement is within a standalone system, I think this
is
exactly what the notepad.exe does, notepad surely works, in its place.
But do we talk about a "standalone system"? I really feel there this is a
little difference between Maven and Notepad... I mean Maven is quite a
global player, building one or the other project over here and there,
whereas Notepad, well, I don't know.
by the way you're actually telling me that the two projects both have
explicit encoding,
OK, then I didn't clearly express myself. With "using UTF-8" I mean that the
sources are indeed UTF-8 encoded, but not necessarily that this encoding is
also declared in the POM.
Regarding SVN/CVS, I think the repository should have of strong type in
case
of encoding, whether explicit or implicit.
e.g. if the SVN repository is using UTF-8, then it's strange if the file
checked out is in another one
about this I don't know much of SVN/CVS, this is an interesting topic I'd
like to know more.
To my knowledge, SVN is currently not aware of file encoding.
Benjamin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
