This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 145256 - Cancelling a Maven unit test does not clear the progress bar.
Summary: Cancelling a Maven unit test does not clear the progress bar.
Status: RESOLVED DUPLICATE of bug 135475
Alias: None
Product: projects
Classification: Unclassified
Component: Maven (show other bugs)
Version: 6.x
Hardware: All Windows XP
: P3 blocker with 3 votes (vote)
Assignee: Milos Kleint
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-27 09:31 UTC by lamski
Modified: 2009-05-25 21:01 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description lamski 2008-08-27 09:31:10 UTC
When a maven project's JUnit tests are being run, a progress bar is shown in the IDE's lower-right corner. When the build is cancelled, the progress bar 
remains until the IDE is restarted. Clicking on the progress bar will show a sub window of running processes. Right-clicking on the cancelled maven JUnit test 
doesn't have the "Cancel Process" menu item enabled.

Running jps in the command line will reveal that maven's surefire-booter is running. Killing the surefire-booter process won't remove the progress bar from 
the IDE.
Comment 1 Milos Kleint 2008-09-11 14:58:54 UTC
duplicate of http://jira.codehaus.org/browse/MEVENIDE-566, I will close that one though as issues are going to be moved
from there to netbeans.org anyway soon.

"it boils down to plexus-utils' CommandLineUtils class. The killProcess method is correctly called on interrupted exception.
http://bugs.sun.com/bugdatabase/view_bug.do;:YfiG?bug_id=4770092 could be related as noted in the killProcess() method
comment. "
Comment 2 tonyj321 2008-11-12 22:27:46 UTC
A little more info. When running tests and looking with process explorer I see:

netbeans.exe->nbexec.exe->nbexec.exe->java.exe->cmd.exe->java.exe->cmd.exe->java.exe

My guess is that the first java.exe is netbeans itself, the second is maven, and the third is the process running the
tests (I run tests in forked mode). When killing the process from netbeans the first cmd.exe gets killed, but the child
java.exe process does not get killed and it then appears as a top level process:

java.exe->cmd.exe->java.exe

So it looks as if the top level cmd.exe is being killed, but not the entire tree of processes. (Using process explorer
to manually kill the java.exe does work)

Comment 3 Milos Kleint 2009-04-10 14:53:34 UTC
duplicate of #135475 it seems 

*** This issue has been marked as a duplicate of 135475 ***