Mario Gutierrez

Unfortunately `godo` does not work in directories outside of GOPATH with this PR. I get `import cycle not allowed` errors. If I remember correctly that's why I settled on `package...

The issues is Go is not very good at process handling. See questions like this on [stackoverflow](http://stackoverflow.com/questions/22470193/why-wont-go-kill-a-child-process-correctly). If somebody can provide a solution to that on Windows, I'd be happy...

@The `Bash` and `Run` functions are sugar functions to aid in setting environment variables, template interpolation. `strings.Join` is an option if you have a slice of args. ``` ctx.Run("app "...

Should be part of the context ``` go p.Task("server", nil, func (c *Context) { fmt.Println(c.FileEvent.Path) }) ```

:( that's not good, i'll take a look later today

To clarify, the initial task run is programmatic and subsequent runs are react to file watch events.

V2 is fairly stable. I have been using it for the past few months. There are a few things to sort out---watching Godofile sometimes leaves an orhpaned process, better docs...

Definitely a problem. I'm surprised I haven't run into that. I'll think of something and should have a fix in the soon.

This might take a couple of days. The solution is to add Start method to the context so the task can track the process and then add a Task.Kill method....

I need to understand your process a bit more. In most cases, if a dependency fails the parent shouldn't be restarted. For example ``` p.Task("server", D{"assets", "views"} ...) ``` If...