Hi Jamis,
I have updated to the latest Cap 2.0.100 but I am still seeing
some issue with the require
and configuration reload in a rails env.
If I run a config reload in a straight ruby env. All is cool the
required files will correctly get reloaded as expected. However in a
rails env, the second configuration load will no load the required
files again.
I have tried different things ie starting the rails env in prod vs
dev but no avail. After a bit of debugging thru the latest code base,
I am finding that the overloaded require behaves differently in these
2 cases. So in the loading.rb file at line ~150 there is a call to
super ie
result = super
Looking at the result value in the rails case it always comes back
as [] vs the expected true|false.
Any ideas ?
-Fernand
--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---
