Re: [mevenide-user] Maven Process not killed when stopping debugger
"Laurent Forêt" <[email protected]>
| Newsgroups | gmane.comp.jakarta.turbine.maven.mevenide.user |
|---|---|
| Message-ID | <[email protected]> |
I have exactly the same behaviour ! When I stop the debug session it stop the test running. But When I click on the stop button in a running session it does not kill the java process launched. I can reproduce it, at will ! I am going to send you a project that fail at home. best regards. On 10/22/07, Milos Kleint <[email protected]> wrote: > > On 10/22/07, Mohni, Daniel <[email protected]> wrote: > > some updates here, > > > > when I kill the debug session with the 'stop' button > > in the toolbar, the maven process is killed correctly. > > > > But when I kill the execution in the status bar the maven process is > > not killed. > > is that repeatedly reproducible? I've checked the code and both UIs > call the same cancel() method. A difference could be that some > projects use the command line execution while others don't. Each has > different implementation of cancel(). > > Milos > > > > > just for the records... > > > > Regards > > > > Daniel > > > > > -----Original Message----- > > > From: Milos Kleint [mailto:[email protected]] > > > Sent: Monday, October 22, 2007 9:30 AM > > > To: [email protected] > > > Subject: Re: [mevenide-user] Maven Process not killed when > > > stopping debugger > > > > > > On 10/18/07, Mohni, Daniel <[email protected]> wrote: > > > > When I run test using surefire and decide to abord the test > > > > using the stop button, the surefire thread keeps running > > > > > > > > Is there a way to kill the surefire thread at the same time than > > > > the maven thread ? > > > > > > hmm.. I would suppose the surefire plugin should be taking care of > > > that. But it's possible it's only working for command-line usage and > > > not taking the embedded maven builds into account. > > > > > > > > > > > I don't know whats the impact on changing the forkMode of the > > > > surefire plugin... (default is once) > > > > > > > > > > I think fork mode is not relevant here. The surefire plugin shall kill > > > it's tests threads/VMs when the main plugin thread dies. From your > > > description it seems that it's not doing it. > > > Best fixed in the surefire plugin I believe. > > > > > > Milos > > > > > > > whats the best option ? > > > > maybe a forkMode option in the configuration panel... > > > > > > > > Regards > > > > > > > > Daniel > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe from this list please visit: > > > > > > > > http://xircles.codehaus.org/manage_email > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe from this list please visit: > > > > > > http://xircles.codehaus.org/manage_email > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe from this list please visit: > > > > http://xircles.codehaus.org/manage_email > > > > > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > >