Wrong post at geotools mailing list forwarded to this list …
---------- Weitergeleitete Nachricht ----------
Von: “Frank Gasdorf” <fgdrf@anonymised.com>
Datum: 29.01.2013 22:31
Betreff: build infrastructure : different behavior/results than on mac osx and windows
An: “geotools-dev” <geotools-devel@lists.sourceforge.net>
hello developers,
I’m pretty confused about different results of deployable artefacts from different build environments at the moment. Whats wrong?
Situation:
-
like the java standard says, properties files should have ISO-8859-1 encodings whereas geoserver (i18n) properties are UTF8 (mentioned in other threads and is off topic right here)
-
if I build on mac and on windows with currently checked in German properties files (ISO-8859-1 btw) the result UI looks fine, all special characters are correct (haven’t changed anything in maven poms, build with 2.2.1 maven and jdk 1.6.0_37 with the following command(s):
mvn clean install -DskipTests -Prelease
mvn assembly:attached -
if I download a war from nightly builds and deploy it into the same container (on mac & win) the “special” chars are incorrect
Whats the problem? If somebody is working on translations and test these on mac and windows the expectation is to get it this way into the release, but it doesn’t.
Who can describe the infrastructure of the CI machine at http://hudson.opengeo.org/hudson ?
Who can confirm or can test on an other linux machine?
Can anybody confirm the problem?
I would like to get the translations into 2.3-beta releases correctly. Should I create a Jira issue for this problem?
Thanks a lot
Frank
PS: Thanks to Stefan Engelhardt for testing and contributing translations!