Bug 96273 - [JUnit] Rerun failed test - failures first doesn't force save
Summary: [JUnit] Rerun failed test - failures first doesn't force save
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows 2000
: P3 trivial with 1 vote (vote)
Target Milestone: 3.4 M2   Edit
Assignee: Markus Keller CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-23 04:04 EDT by Ben Aveling CLA
Modified: 2007-08-27 11:36 EDT (History)
1 user (show)

See Also:

Attachments
Patch (1.64 KB, patch)
2005-06-07 07:06 EDT, David Saff CLA 		no flags Details | Diff
Show Obsolete (1) View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ben Aveling CLA 2005-05-23 04:04:17 EDT 
Unlike "rerun last test", "rerun failed test - failures first"
doesn't ask the user if they want to save any changes. It just 
starts Junit.  

Still a great feature!
Comment 1 Dirk Baeumer CLA 2005-05-23 07:06:34 EDT 
Since we ask for save in other situations we should do here as well. However,
time permitted.
Comment 2 David Saff CLA 2005-06-07 07:06:10 EDT 
Created attachment 22501 [details]
Patch

Makes failures-first launching consistent with regular re-launching.
Comment 3 Markus Keller CLA 2007-08-27 11:36:42 EDT 
In HEAD, Debug already asks the users to save dirty resources.

Released something similar to the patch to make use of the background launching support in DebugUITools.launch(..).