Community
Participate
Working Groups
Sometimes entries in the error log as made by an entry with a simple message, and many subentries with more detailed stack traces, etc. The report as bug action should include the subentries too, if you invoke it from a top-level entry. Actually it is hard to report if you have many subentries because you would have to manually copy each of them.
That sounds like a great idea. Would you be interested in providing a patch Willian?
Created attachment 87439 [details] Patch It asks the user to include subentries if it has any. I did manual tests using a 3 level log entry creating a local task. BTW, I found it strange that the class NewTaskFromErrorAction is in mylyn.bugzilla.ide project, since it is a generic functionality. The first place I tried was in mylyn.pde.ui.
Created attachment 87440 [details] mylyn/context/zip
Thanks Willian! Patch applied, but not yet verified because I didn't have a log entry with subentries around (left a note in the New & Noteworthy to review the UI). I changed the text to "Include children of this entry in the report?" since I'm not sure if the word "subentry" is commonly recognized. Regarding the location of this class, yes, everything in the current ..mylyn.bugzilla.ide plug-in is a candidate to be moved for 3.0, added note to: http://wiki.eclipse.org/Mylyn_Porting_Guide#Pending_Changes_for_Mylyn_3.0
Is all logs put into the description text? I am bit concerned that it would make it too long and in result less readable. Maybe such large logs should be posted as attachments, and then provide a convenience feature to open log in the Error Log view, which allows to import logs for browsing (though I am not sure if these actions are public api).
Created attachment 87913 [details] Error log with 3 levels for testing purposes If anyone want to test, just import this file into error log.
(In reply to comment #5) > Is all logs put into the description text? I am bit concerned that it would make > it too long and in result less readable. > > Maybe such large logs should be posted as attachments, and then provide a > convenience feature to open log in the Error Log view, which allows to import > logs for browsing (though I am not sure if these actions are public api). I like this idea. I opened bug#216640 and bug#216642. I didn't open a bug for the attachment -> error log visualization yet, because I think it is better to have the attachment story completed first. But I wonder how to make this kind of automatic? Maybe attach error log entries using a custom mime-type would be the best approach?
