Without changing the current implementation, we could use a "keep alive" approach to manage the launched process. With this approach the plugin would be responsible for sending a keep alive ping to the launched process. The launched process would kill itself if it didn't receive a ping in a specified amount of time. This way, there can be an option in the plugin to stop the build (which would essentially stop sending keep alive requests).
Just a thought, I've done something similar to manage the life cycle of an out of process embedded web server. -Evan On Mon, Mar 31, 2008 at 1:23 PM, Wendy Smoak <[EMAIL PROTECTED]> wrote: > On Mon, Mar 31, 2008 at 11:12 AM, Shane Isbell <[EMAIL PROTECTED]> > wrote: > > > The VS addin directly handles the modification of the poms, independent > of > > the maven embedder service, so that part would not be affected by > either > > solution. > > Okay, thanks. Back to the original question then. :) > > One thing that was raised in the JIRA issue is: 'canceling an executed > nmaven command in VS'. > > Leopoldo, are you talking about an individual build, or the ability to > stop the Add-in altogether? > > I'm interested in the latter, since I've noticed that I can't do a > command line build after building with the VS Add-in. (Maven > complains about files being in use.) There doesn't seem to be a way > to stop it without exiting Visual Studio (and then it doesn't always > stop... sometimes I have to kill a Java process.) > > So yes, there are some issues with the separate long-running process, > but I'm not yet convinced that discarding it entirely is the way to > go. > > -- > Wendy >
