No the multi-stage "task" is slightly special, and it doesn't work as you might expect!
There's not a lot standing between a special "all" name which would call both "setup" tasks, but unfortunately it doesn't exist right now, because… The two stage names "production" and "staging "are "meta tasks", which multistage creates via the loading of the plugin. Multistage loads file with the matching stage-name, in the context of the current deployment, setting variables, etc as you can see in the stage-specific configuration files... The thing that's missing from this is that unless the first task name is a pre-existing "stage" meta task, when using multi-stage an error is raised (so you couldn't even make your own "all" task). And secondly, would that be possible, the 2nd file loaded (stage file) would presently overwrite the values defined in the first. Rafa's suggestion is the sanest, although it is clearly a workaround/hack. - Lee -- * You received this message because you are subscribed to the Google Groups "Capistrano" group. * To post to this group, send email to capistrano@googlegroups.com * To unsubscribe from this group, send email to capistrano+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/capistrano?hl=en
