Fix ContentScanner.nextToken() logic to avoid use exception for flow control ---------------------------------------------------------------------------- Key: JBIDE-19983 URL: https://issues.redhat.com/browse/JBIDE-19983 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: freemarker Affects Versions: 4.3.0.Beta1 Reporter: Denis Golovin Assignee: Denis Golovin Priority: Minor Fix For: 4.16.x Currently ContentScanner.nextToken() tests chars without detecting EOF first. It tiggers BadLocationException and catch block then decide what to do next.