Community
Participate
Working Groups
Files that are checked in in our source control system (starteam) have a header with the local filename in the filecomment. Since the starteam client only runs on windows, the path will contain backslashes. If one of these backslashes is followed by a letter 'u', it will be considered as a unicode escape sequence. This blocks me from compiling classes that contains paths like that (which means all my files in that project, since the package structure is "com.ubizen.sdp"). Eclipse worked fine for me until I checked in my sources, now they contain the full pathname in the filecomment, and the compiler won't compile them, so I consider this to be a blocker.
JLS 3.2 explains that unicode translation occurs prior to tokenization. Therefore invalid unicode sequences are reported inside comments. Javac produces the same error. /** * \u\X.java is invalid * \\u\X.java is fine */ public class X { } This is a bug of the source control system you're using, which ends up producing illegal Java source files according to the specs.
see also: Bug 6677
