I like the idea: easier to do than having access to a Z/OS box (anyone able to deploy a CI on a Z/OS box?), even if every aspect is not covered (for example it doesn't fail if encoding parameter has not been set in compiler plugin)
But if we do so on a whole CI server, I fear the havoc will be bigger than expected and we'll need a lot of work to fix everything and have a stable situation: I'm working on encoding in XML files for a long time now, which is a part of the overall encoding question, and even on this part, I know everything is not yet fixed. I just tried manually to check the result of such a configuration. I found that building any plugin fails: there are problems when scanning mojo. We'll need to fix this general problem before setting this option on a whole CI server. The problem starts with maven-plugin-plugin: when 2.4.1 release is out (for Maven 2.0.9), we'll be able to work on it. I was able to build components/branches/maven-2.0.x: with PLX-343 and PLX-367 being fixed in svn but not integrated in Maven 2.0.x, I expected a failure while reading classworlds configuration then plexus configuration. I was surprised, but it seems to work better than expected (I'd really like to understand why...). All in all, if the configuration can be set component by component, I have no problem. But if the whole CI is impacted, I think we'll need some work before setting the configuration. regards, Hervé Le vendredi 21 mars 2008, Benjamin Bentmann a écrit : > Hi, > > There are still several code spots in Maven that rely on the platform's > default encoding when processing text files which does support build > reproducibility. It could help developers to detect such defects if the CI > machines were configured to run Maven with > > MAVEN_OPTS=-Dfile.encoding=UTF-16 > > This setting will wreck havoc on any component that assumes ASCII, UTF-8 or > Latin-1 when converting between characters and bytes. > > Ciao, > > > Benjamin > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
