Changed AbstractAntlrParserAdapter to catch all exceptions during par…

[TwoOfTwelve]

This makes it, so all antlr exceptions are caught, so that the name of the file, that failed is always shown.
Addresses: #1386

[dfuchss]

Isn't Exception enough ?

[TwoOfTwelve]

It would probably be enough, but I think it could also help printing the file in case on OutOfMemoryError or similar things, especially since the original exception will still be printed as the cause.

[dfuchss]

I also had this kind of Errors in mind. Nevertheless, I won't catch this kind of Error since this kind of errors can't be handled in a good way. Catching a OutOfMemoryError won't solve the problem as far as I remember :)

But I don't have a strong opinion on what to catch here :)

[TwoOfTwelve]

This catch does not really handle the error, but instead adds some additional information for the user, so I would consider it a form of logging. The intention is not to continue if anything happens here. Just for reference I have tried this with a small example:

import java.util.ArrayList;
import java.util.List;

public class OutOfMemoryTest {
    public static void main(String[] args) {
        try {
            List<int[]> items = new ArrayList<>();
            for (int i = 0; i < Integer.MAX_VALUE; i++) {
                items.add(new int[Integer.MAX_VALUE]);
            }
        } catch (Throwable e) {
            throw new RuntimeException("Some error happened.", e);
        }
    }
}

If you compile and run this code the following error will be printed:

Exception in thread "main" java.lang.RuntimeException: Some error happened.
	at OutOfMemoryTest.main(OutOfMemoryTest.java:12)
Caused by: java.lang.OutOfMemoryError: Requested array size exceeds VM limit
	at OutOfMemoryTest.main(OutOfMemoryTest.java:9)

In our case, this would give the user the information which source file caused the error to happen. In the end I would leave the decision up to @tsaglam.

[tsaglam]

One is better for API users, the other for application users. Let us go with Exception for now, we can always change it.