[Patch] Adding a new bug report queue.

[michael2402]

Add a new queue that handles bug report dialog display.

We do not need MapView to check for an active exception handling dialog. If the exception happens again, it will be added to the queue. A good guess is done to allow the user to suppress duplicate messages, so the user is still able to save if e.g. rendering fails.

[Don-vip]

does not apply cleanly

[Don-vip]

            try {
                e.printStackTrace();
            } catch (RuntimeException e2) {
                // we cannot do anything more...
                // re-throwing this causes an infinite loop.
            }

Isn't it a bit overkill? Did you really find a case where printStackTrace throws an exception?

[michael2402]

I wanted to overwrite it in ReportedException to only print the real, original stack trace. printStackTrace also calls getMessage() which may be implemented by an user to e.g. format the message.

But yes, it is very unlikely to happen ;-).

[Don-vip]

In 10819/josm:

fix #13352 - new bug report queue (patch by michael2402) - gsoc-core

[Don-vip]

The unit test does not work: job/JOSM/lastCompletedBuild/jdk=JDK8/testReport/org.openstreetmap.josm.tools.bugreport/BugReportExceptionHandlerTest/testHandleException/