<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to 412: Suppress CheckstyleException due to antlr.Parser.match expecting EOF, found '&lt;&lt;'</title><link>https://sourceforge.net/p/eclipse-cs/bugs/412/</link><description>Recent changes to 412: Suppress CheckstyleException due to antlr.Parser.match expecting EOF, found '&lt;&lt;'</description><atom:link href="https://sourceforge.net/p/eclipse-cs/bugs/412/feed.rss" rel="self"/><language>en</language><lastBuildDate>Mon, 08 Jan 2018 10:06:34 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/eclipse-cs/bugs/412/feed.rss" rel="self" type="application/rss+xml"/><item><title>#412 Suppress CheckstyleException due to antlr.Parser.match expecting EOF, found '&lt;&lt;'</title><link>https://sourceforge.net/p/eclipse-cs/bugs/412/?limit=25#278f/7c3b</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;You are probably right, as long as CS (Core) only throws you (eclipse-cs) a general CheckstyleException, it will be very difficult for you to distinguish a parsing error from "honest bugs in Checkstyle core" ... I guess the "right" way would be for CS Core to throw a  CheckstyleSourceParseException kind of thing instead a CheckstyleException if the cause is a MismatchedTokenException, and others like that?&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Michael Vorburger</dc:creator><pubDate>Mon, 08 Jan 2018 10:06:34 -0000</pubDate><guid>https://sourceforge.netf1e172f563f1edb3a9da137b89b9d8b53602365f</guid></item><item><title>#412 Suppress CheckstyleException due to antlr.Parser.match expecting EOF, found '&lt;&lt;'</title><link>https://sourceforge.net/p/eclipse-cs/bugs/412/?limit=25#278f</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;If this would be done (it could, presumably), how would one discern those exceptions from honest bugs in Checkstyle core?&lt;/p&gt;
&lt;p&gt;Back in the day, eclipse-cs used to pop up an error dialog, which was truly disturbing.&lt;br/&gt;
Nowadays it just logs an Checkstyle error, like "hey, something unexpected happened, please check the error log if you care" - which I think is pretty unobtrusive, while still retaining all the information needed for bug hunting.&lt;/p&gt;
&lt;p&gt;How would you propose to solve this?&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lars Koedderitzsch</dc:creator><pubDate>Wed, 20 Dec 2017 08:33:51 -0000</pubDate><guid>https://sourceforge.net5598b3dc3ed6eda0eb5512653f6a43c2b4cf552e</guid></item><item><title>Suppress CheckstyleException due to antlr.Parser.match expecting EOF, found '&lt;&lt;'</title><link>https://sourceforge.net/p/eclipse-cs/bugs/412/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;In general, it's useful of course that eclipse-cs surfaces unexpected internal CS errors by propagating its exceptions into Eclipse' Error Logs and sometimes pop up into your face.&lt;/p&gt;
&lt;p&gt;There is one particular condition however which I've faced a number of times which IMHO in an ideal world would be nice to suppress - the one shown below. That one is, of course, caused by me being in the middle of a conflict resolution (with EGit, but whatever the cause). I know my .java is invalid; it's got JDT's red error markers all over it - I don't need CS to jump in. If there is a Lexer/Parser exception, perhaps even one specifically one related to "&amp;gt;&amp;gt;", then just shut up?&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;com.puppycrawl.tools.checkstyle.api.CheckstyleException: Exception was thrown while processing /home/vorburger/dev/ODL/git/netvirt/vpnservice/elanmanager/elanmanager-impl/src/main/java/org/opendaylight/netvirt/elan/utils/ElanUtils.java
    at com.puppycrawl.tools.checkstyle.Checker.processFiles(Checker.java:281)
    at com.puppycrawl.tools.checkstyle.Checker.process(Checker.java:196)
    at net.sf.eclipsecs.core.builder.Auditor.runAudit(Auditor.java:159)
    at net.sf.eclipsecs.core.jobs.AuditorJob.runInWorkspace(AuditorJob.java:82)
    at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: com.puppycrawl.tools.checkstyle.api.CheckstyleException: MismatchedTokenException occurred during the analysis of file /home/vorburger/dev/ODL/git/netvirt/vpnservice/elanmanager/elanmanager-impl/src/main/java/org/opendaylight/netvirt/elan/utils/ElanUtils.java.
    at com.puppycrawl.tools.checkstyle.TreeWalker.processFiltered(TreeWalker.java:193)
    at com.puppycrawl.tools.checkstyle.api.AbstractFileSetCheck.process(AbstractFileSetCheck.java:78)
    at com.puppycrawl.tools.checkstyle.Checker.processFile(Checker.java:301)
    at com.puppycrawl.tools.checkstyle.Checker.processFiles(Checker.java:271)
    ... 5 more
Caused by: /home/vorburger/dev/ODL/git/netvirt/vpnservice/elanmanager/elanmanager-impl/src/main/java/org/opendaylight/netvirt/elan/utils/ElanUtils.java:23:1: expecting EOF, found '&amp;lt;&amp;lt;'
    at antlr.Parser.match(Parser.java:211)
    at com.puppycrawl.tools.checkstyle.grammars.GeneratedJavaRecognizer.compilationUnit(GeneratedJavaRecognizer.java:211)
    at com.puppycrawl.tools.checkstyle.TreeWalker.parse(TreeWalker.java:440)
    at com.puppycrawl.tools.checkstyle.TreeWalker.processFiltered(TreeWalker.java:175)
    ... 8 more
&lt;/pre&gt;&lt;/div&gt;

&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Michael Vorburger</dc:creator><pubDate>Wed, 02 Nov 2016 11:17:26 -0000</pubDate><guid>https://sourceforge.neta428657634a75759f5c58f26924df894b4d3416d</guid></item></channel></rss>