I wouldn't bother with the script/plugin command for your own engines - why not just set SVN externals to your engine repositories and use 'svn update' to pull in the latest changes?
- james On 3/21/06, Lance Ditkins <[EMAIL PROTECTED]> wrote: > I've created a couple of engines for use with some internal projects > here and stuck them in their own svn repos. > > Then I have other svn-stored projects I want to use the engines with. > Both the projects and the engines are updated quite a bit. > > So I install the engine from my project: script/plugin install > http://<path_to_engine_repo>/<engine_name> > > Then later I commit some changes to the engine. > > So then I go to my project and try to update the plugin: script/plugin > update <engine_name> > > I get: "Updating plugin: <engine_name> " and no errors as a result. > > But the source code of the engine is NOT updated in the project. Arrg. > Any ideas? (I would hate to blow away my engine with an rm -rf and > reinstall everytime I make a tweak) > > Any suggestions appreciated! Thanks! > > (X posted on the RoR list, got a nil response) > > -- > Posted via http://www.ruby-forum.com/. > _______________________________________________ > engine-developers mailing list > [email protected] > http://lists.rails-engines.org/listinfo.cgi/engine-developers-rails-engines.org > -- * J * ~ _______________________________________________ engine-developers mailing list [email protected] http://lists.rails-engines.org/listinfo.cgi/engine-developers-rails-engines.org
