On 1/24/07, Jason Lee <[EMAIL PROTECTED]> wrote: > I guess the bigger question for some of us (myself included) that > have dependencies on this is: what now? > > Pull the code into my project and maintain it myself? And for me, > it's not just login engine, but also user engine. I suppose I'll just > roll it into my app and make the necessary changes.
What I'd recommend you do depends on your plans with Rails. If you don't need to upgrade to Rails 1.2.... you're fine. Just ensure that any externals are properly locked-down to tags, or secured with Piston. If you ARE upgrading to Rails 1.2, you have two basic options: 1. copy the controllers, models and so on into your own app. 2. take a dump of the current login/user engines and import it into your own repository - you *are* all using version control, right? Then update them to work with Rails 1.2 as plugins that play nicely with the new engines and rails releases. Document it a bit. Hell, maybe even share it with the world... -- * J * ~ _______________________________________________ engine-users mailing list [email protected] http://lists.rails-engines.org/listinfo.cgi/engine-users-rails-engines.org
