Gradle 2.3 + JUnit 4.11 =破碎的Charset

时间:2015-03-01 00:43:55

标签: java unicode junit character-encoding gradle

在正常情况下将正确的字节写入文件,但结合Gradle 2.3 + JUnit 4.11意外结果。

import org.junit.Test;
import java.io.FileOutputStream;
import static org.junit.Assert.*;

public class TestUTF16Test
{
   @Test
   public void testWrite() throws Exception
   {
      try (FileOutputStream bin = new FileOutputStream("testUTF16junit.txt")) {
         bin.write("Русский".getBytes("UTF-16LE"));
      }
   }
}

的build.gradle

apply plugin: 'java'

sourceCompatibility = 1.7
version = '1.0'

repositories {
    mavenCentral()
}

dependencies {
    testCompile group: 'junit', name: 'junit', version: '4.11'
}

$ gradle.bat:clean:test

:clean
:compileJavawarning: [options] bootstrap class path not set in conjunction with -source 1.7
1 warning

:processResources UP-TO-DATE
:classes
:compileTestJavawarning: [options] bootstrap class path not set in conjunction with -source 1.7
1 warning

:processTestResources UP-TO-DATE
:testClasses
:test

BUILD SUCCESSFUL

Total time: 4.999 secs

结果:

20 04 A0 00 21 04 53 04 21 04 03 04 21 04 03 04... 28 bytes

但它应该是:

20 04 43 04 41 04 41 04 3A 04 38 04 39 04 = 14 bytes

操作系统:Microsoft Windows 7 [版本6.1.7601]

1 个答案:

答案 0 :(得分:1)

Gradle fix

[ compileJava, compileTestJava ]*.options*.encoding = 'UTF-8'

2015,javac无法识别BOM的Unicode!

>javac.exe src\test\java\TestUTF16Test.java
src\test\java\TestUTF16Test.java:1: error: illegal character: '\u00bb'
я╗┐import org.junit.Test;
 ^
1 error

>javac.exe -version
javac 1.8.0_25

现在我理解为什么IDE没有添加BOM ...