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.
Summary: | Cancelling a Maven unit test does not clear the progress bar. | ||
---|---|---|---|
Product: | projects | Reporter: | lamski <lamski> |
Component: | Maven | Assignee: | Milos Kleint <mkleint> |
Status: | RESOLVED DUPLICATE | ||
Severity: | blocker | ||
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | Windows XP | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
lamski
2008-08-27 09:31:10 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. " 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) duplicate of #135475 it seems *** This issue has been marked as a duplicate of 135475 *** |