On 29/04/2011, at 8:47 PM, Magnus Rundberget wrote: > Hi, > > This might be related to : GRADLE-1267
It's not quite the same. That issue refers to the encoding used for the contents of files which need to be filtered. It sounds like your issue is instead related to the encoding used for file names. > > I have a project where someone thought it a good idea to use Norwegian > special characters for naming java classes. æ ø and å. So the files are > encoded as iso-8859-1. > > - I have a project A and B. B depends on A. > - Compilation fails for B because it depends on a class in the jar of A. The > class in question uses a norwegian character in its name. > > When I look in the build/classes/main folder for A I can see that the file > name for the class is correct > However in the jar file for A I can see that the filename has been "mangled" > > So I'm guessing that the jar task (extending copy ?) doesn't use the encoding > it should.. and I can't find any setting for the jar task that I could use to > specify the encoding either. Is there something obvious I'm missing ? > > > cheers > Magnus -- Adam Murdoch Gradle Co-founder http://www.gradle.org VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com
