On Jun 7, 2006, at 9:01 PM, Trevor Squires wrote:
Hey,
I too have felt the pain of having to restart the server when
working on the modules in plugins.
However it's easily avoided by putting a require_dependency
'my_module' just before the include MyModule call. It's a small
amount of
On 8-jun-2006, at 6:01, Trevor Squires wrote:
However it's easily avoided by putting a require_dependency
'my_module' just before the include MyModule call. It's a small
amount of pain that I only have to bear during development so it's
okay with me.
Thanks for the tip Trevor!
--
Juli
Hey,
I too have felt the pain of having to restart the server when working
on the modules in plugins.
However it's easily avoided by putting a require_dependency
'my_module' just before the include MyModule call. It's a small
amount of pain that I only have to bear during development so
On 8-jun-2006, at 1:31, Blair Zajac wrote:
There's a scenario with the projects I'm working on that could use
reloadable modules, instead of just reloadable classes.
Ticket and patch with test suite changes are at:
http://dev.rubyonrails.org/ticket/5329
I am now building an app that assem
There's a scenario with the projects I'm working on that could use reloadable
modules, instead of just reloadable classes.
Ticket and patch with test suite changes are at:
http://dev.rubyonrails.org/ticket/5329
The reasoning for doing this is I have a library of 25 and growing plugins that
de
