Bug 152869 - allow to create new issues from JUnit stack trace
Summary: allow to create new issues from JUnit stack trace
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: unspecified   Edit
Hardware: PC All
: P3 enhancement (vote)
Target Milestone: 2.2   Edit
Assignee: Frank Becker CLA
QA Contact:
URL:
Whiteboard:
Keywords: noteworthy
Depends on:
Blocks: 169426
  Show dependency tree
 
Reported: 2006-08-04 14:44 EDT by Eugene Kuleshov CLA
Modified: 2007-11-15 17:34 EST (History)
4 users (show)

See Also:


Attachments
patch (15.02 KB, patch)
2007-11-03 18:54 EDT, Frank Becker CLA
no flags Details | Diff
mylyn/context/zip (11.38 KB, application/octet-stream)
2007-11-03 18:54 EDT, Frank Becker CLA
no flags Details
New Patch (6.53 KB, patch)
2007-11-03 19:06 EDT, Frank Becker CLA
no flags Details | Diff
mylyn/context/zip (13.75 KB, application/octet-stream)
2007-11-03 19:06 EDT, Frank Becker CLA
no flags Details
Patch replace attachment 82039 and 82041 (6.41 KB, patch)
2007-11-04 15:33 EST, Frank Becker CLA
no flags Details | Diff
mylyn/context/zip (15.18 KB, application/octet-stream)
2007-11-04 15:33 EST, Frank Becker CLA
no flags Details
mylyn/context/zip (16.18 KB, application/octet-stream)
2007-11-14 20:27 EST, Robert Elves CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Eugene Kuleshov CLA 2006-08-04 14:44:39 EDT
Allow to create new issues from JUnit stack trace. In a way it is very similar to what is already done for PDE's Error Log view.
Comment 1 Robert Elves CLA 2006-08-09 14:45:51 EDT
Jeff, since you did this for the error log it makes sense that you take this one.  If you aren't interested just say the word.
Comment 2 Mik Kersten CLA 2007-09-11 01:11:24 EDT
Raising priority because we need this internally to help maintain the health of the unit test suite.
Comment 3 Frank Becker CLA 2007-11-03 10:51:04 EDT
 (In reply to comment #2)
> Raising priority because we need this internally to help maintain the health of
> the unit test suite.

Is it OK that I look at this. I think it is somehow related to bug 169426 so I think it is not to difficult.
Comment 4 Frank Becker CLA 2007-11-03 18:54:22 EDT
Created attachment 82039 [details]
patch

I found only a way to add the action in the upper part of the JUnit view.

Please look if this is what you expect.
Comment 5 Frank Becker CLA 2007-11-03 18:54:28 EDT
Created attachment 82040 [details]
mylyn/context/zip
Comment 6 Frank Becker CLA 2007-11-03 19:06:11 EDT
Created attachment 82041 [details]
New Patch

Sorry in my patch was by mistake parts of bug 206510 and the change of the MANIFEST.MF was not included.
Comment 7 Frank Becker CLA 2007-11-03 19:06:19 EDT
Created attachment 82042 [details]
mylyn/context/zip
Comment 8 Frank Becker CLA 2007-11-04 15:33:24 EST
Created attachment 82059 [details]
Patch replace attachment 82039 [details] and 82041

I add support for enable the Action only if a trace is available.
Comment 9 Frank Becker CLA 2007-11-04 15:33:33 EST
Created attachment 82060 [details]
mylyn/context/zip
Comment 10 Robert Elves CLA 2007-11-14 20:27:33 EST
Great Frank. Patch applied and ip log updated. Just updated some class names and ids prior to committing. Note that we may need to review this added dependency on JDT at some point.
Comment 11 Robert Elves CLA 2007-11-14 20:27:36 EST
Created attachment 82927 [details]
mylyn/context/zip
Comment 12 Robert Elves CLA 2007-11-14 20:28:56 EST
Once available we can use the api from bug#209402 to populate the new bug.
Comment 13 Mik Kersten CLA 2007-11-15 02:25:51 EST
Excellent!  Great stuff Frank.

This action is JDT/Junit specific, and as such is better in the org.eclipse.mylyn.java.ui plug-in, so I moved it there.  I also renamed it to "New Task from Failure..." and used the standard New Task icon.  I also changed the string "Error Log" to "Failure Log".

Frank: Note that this fails for local tasks.  Would you like to reopen (if you're going to work on it) or create a new bug for that (if not)?
Comment 14 Steffen Pingel CLA 2007-11-15 03:36:15 EST
I agree. That is a cool new feature that should be mentioned in the New & Noteworthy. Thanks Frank.

> Frank: Note that this fails for local tasks.  Would you like to reopen (if
> you're going to work on it) or create a new bug for that (if not)?

This code is currently under going a major refactoring (bug 209892) that will generalize support for populating the editor when creating new tasks. Please hold off until all changes to bug 169426 and subtasks have been completed.