#1489 [java] Issue with Byte Order Mark

[Hari94]

This Bug occures if the Source file starts with zero width no-break space.
To simplify matters take a look at the attachment.

Processing C:\Users\Username\Java_programm.jar:myPackage.path/SampleClass.java
Error while processing file: C:\Users\Username\Java_programm.jar:myPackage.path/SampleClass.java
net.sourceforge.pmd.lang.ast.TokenMgrError: Lexical error in file C:\Users\Username\Java_programm.jar:myPackage.path/SampleClass.java at line 1, column 1. Encountered: "\ufeff" (65279), after : ""
at net.sourceforge.pmd.lang.java.ast.JavaParserTokenManager.getNextToken(JavaParserTokenManager.java:2263)
at net.sourceforge.pmd.lang.java.ast.JavaParser.<init>(JavaParser.java:10903)
at net.sourceforge.pmd.lang.java.AbstractJavaParser.createJavaParser(AbstractJavaParser.java:42)
at net.sourceforge.pmd.lang.java.Java18Parser.createJavaParser(Java18Parser.java:23)
at net.sourceforge.pmd.lang.java.AbstractJavaParser.parse(AbstractJavaParser.java:56)
at net.sourceforge.pmd.SourceCodeProcessor.parse(SourceCodeProcessor.java:91)
at net.sourceforge.pmd.SourceCodeProcessor.processSource(SourceCodeProcessor.java:138)
at net.sourceforge.pmd.SourceCodeProcessor.processSourceCode(SourceCodeProcessor.java:76)
at net.sourceforge.pmd.SourceCodeProcessor.processSourceCode(SourceCodeProcessor.java:43)
at net.sourceforge.pmd.processor.PmdRunnable.call(PmdRunnable.java:79)
at net.sourceforge.pmd.processor.PmdRunnable.call(PmdRunnable.java:25)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)</init>

[Andreas Dangel]

Hm... javac doesn't compile it:

javac Main.java
Main.java:1: error: illegal character: '\ufeff'
public class Main
^
1 error

Java source code obviously can't start with a BOM....

[Andreas Dangel]

PMD could filter out the BOM of the source file and ignore/hide the problem. However, since you can't compile the source file, the auxclasspath feature of PMD won't work and you might have false positives/false negatives for some rules.

Therefore, this issue won't be fixed.

Workaround is, to remove the BOM.

See also:

• http://bugs.java.com/view_bug.do?bug_id=4508058
• http://stackoverflow.com/questions/9811382/compiling-javac-a-utf8-encoded-java-source-code-with-a-bom
• http://stackoverflow.com/questions/17555504/illegal-character-65279-during-maven-compile-despite-being-set-to-utf-8