Yep, that's the only test that fails. I think that gradle is handling things fine, but our test fixtures use the file name, which is reported incorrectly. The fixtures don't actually need to read the file name, since they create the file in the first place. So that's a potential avenue for a fix. I did something like that to get the ivy fixtures handling layouts better. But I'm hopeful there's a simple JVM/OS fix. Daz On 27 Apr 2014 15:51, "Adam Murdoch" <adam.murd...@gradleware.com> wrote:
> > On 28 Apr 2014, at 2:56 am, Daz DeBoer <darrell.deb...@gradleware.com> > wrote: > > G'day > I'm getting failures running the new non-ascii character test in > MavenHttpRepoResolveIntegrationTest on my Mac. When debugging, it seems > like File.getCanonicalPath() is converting all non-ascii characters to '?'. > > I've got 'file.encoding' set to 'UTF-8' for the test process, and I'm > running with JDK 1.7.0_25. > > Is anyone else seeing this problem? Any hints? > > > I'll take a look. > > Do the non-ascii tests in the 'ivy' and 'maven' projects work for you? > > > -- > Adam Murdoch > Gradle Co-founder > http://www.gradle.org > VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting > http://www.gradleware.com > > Join us for Gradle Summit 2014, June 12th and 13th in Santa Clara, CA: > http://www.gradlesummit.com > >
