It doesn't, always. I ran into this too -- "svn export" ignores externals with some versions of svn.
The workaround was to replace that with an rsync command, cloning the entire tree, excluding the .svn directories. Have you tried an export with the svn which is actually installed on the server? On Mon, Jun 9, 2008 at 11:17 PM, Jamis Buck <[EMAIL PROTECTED]> wrote: > > Cap doesn't do anything special with svn:externals. It's SCM module > wrapper just executes "svn export" when asked to export, which ought to > export the externals, too. > > - Jamis > > cjharrelson wrote: > > Whenever I do a deploy, my externals are not being exported. Is there > > something I need to do to get this to happen or is it the default way > > cap should behave on an export? > > > > Thanks! > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
