Hi, when fixing the issue in CAMEL-6854 we have created a change in the test in a way that will recreate the described issue, however only on Windows (or a different platform where the platform encoding is not UTF-8). On a UNIX or Linux platform with UTF-8 default encoding the test will succeed even without the patch. Is there a better way to put that into the build?
Best regards Stephan