I have some creative ideas how to implement it ;-) I will create a prototype for review ...
If anyone wants to try please check out the prototypes repository on branch deadlock_detector_206328, run the (only) test in the module and you will see how the deadlocks are submitted. Feedback welcome ;-)
The status is now started ...
One word of explanation: I did not include the whole thread dump in the URL because some web browsers (most notably IE) have some limits on URL length. So the thread dump is saved into a file and the user is asked to paste the thread dump into the newly created issue. At the same time I open the text editor with the thread dump ;-)
One more change: the thread dump is generated directly into the logger - no need to create a separate file or submit it by the user. The exception reporter will find the log entries in the log and report them on the subsequent start.
I am preparing to merge the branch into the trunk after 227668 was integrated.
Integrated into 'main-golden', will be available in build *201305172300* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
User: David Strupl <firstname.lastname@example.org>
Log: #206328: Initial implementation of deadlock detector and reporter.
(transplanted from 018346b67ccd805ff3785d6c63621858748731d8)