It might be a good idea to run CI with IBM JDK even on more common
hardware. For example, I could not build maven with IBM JDK last time I
tried. I did not have much time to investigate, but it looked like IBM
JDK could not read modello's pom.xml as UTF-8.
--
Regards,
Igor
Hervé BOUTEMY wrote:
AFAIK, the problem doesn't show for japanese nor chinese developers: even in
Japan or China, platform encoding on Unix or Windows is ASCII based,
precisely to avoid problems on "simple" ascii characters
like Benjamin says, the encoding issue is more subtle
There is one situation I know for this encoding issue, where a developer
cannot use Maven: it is Z/OS, where platform encoding is EBCDIC which is not
ASCII based. MANTTASKS-14 is a report of such a problem.
But as there is not much Java developers on Z/OS, there are few reports and
few testers for improvements: hence the good idea from Benjamin to force
UTF-16 on CI machines.
BTW, if anybody has a Z/OS box, I'll be glad to have some testers on
MANTTASKS-14 :)
regards
Hervé
Le lundi 24 mars 2008, Benjamin Bentmann a écrit :
does this mean maven actually never worked fro japanese or chinese
developers?
It depends: As long as one sticks to US-ASCII when editing source files and
uses a platform encoding that has US-ASCII as a subset (UTF-8, Latin-X,
...), you won't notice Maven's misbehavior. Also, using Non-ASCII
characters could work if all development machines use the same default
encoding (preferably UTF-8 for best harmony with the XML readers/writers).
The encoding issue is really subtle because it only shows up in
certain/rare situations. That's why I suggest to configure the CI machines
to UTF-16 some day in the future such that at least some tests run in an
edge-case environment.
Benjamin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
