Sounds good to me Rick.
On 12/27/06, Rick Olson <[EMAIL PROTECTED]> wrote:
Hey guys, I thought we were all ready for a new Rails 1.2 RC, but I
just realized I had cache_classes=true in one of my apps, and it
started bombing as soon as I changed it back. So here's the
changeset: http://dev.rub
Hey guys, I thought we were all ready for a new Rails 1.2 RC, but I
just realized I had cache_classes=true in one of my apps, and it
started bombing as soon as I changed it back. So here's the
changeset: http://dev.rubyonrails.org/changeset/5801
Nicholas' load_once_path changes were working, bu
> No brainer patch to apply: http://dev.rubyonrails.org/ticket/6842
Applied this and 6851 to trunk and 1.2. Thanks!
--
Cheers
Koz
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Core" group.
To
On 12/15/06, Aaron Pfeifer <[EMAIL PROTECTED]> wrote:
> I agree with James. I'm not really sure why it was added there in the
> first place (plus it's really not correct either since it doesn't add
> plugins in subdirectories). So with his solution, we get fix 2
> problems with 1 stone.
It occu
I agree with James. I'm not really sure why it was added there in the
first place (plus it's really not correct either since it doesn't add
plugins in subdirectories). So with his solution, we get fix 2
problems with 1 stone.
James Adam wrote:
> On 12/15/06, Michael Koziarski <[EMAIL PROTECTED]
On 12/15/06, Michael Koziarski <[EMAIL PROTECTED]> wrote:
> Having said that, a patch to tidy all that up, and make config.plugins
> a little more powerful does seem reasonable.
As promised: http://dev.rubyonrails.org/ticket/6851
Is there *any* chance that this change might be included in 1.2?..
On 12/15/06, Michael Koziarski <[EMAIL PROTECTED]> wrote:
>
> > "The recent addition of config.plugins will let you specify which
> > plugins to load, and which order to load them in."
> > (http://dev.rubyonrails.org/ticket/6418)
>
> config.plugins prevents the init.rb from being called, meaning
> "The recent addition of config.plugins will let you specify which
> plugins to load, and which order to load them in."
> (http://dev.rubyonrails.org/ticket/6418)
config.plugins prevents the init.rb from being called, meaning the
plugins 'lie dormant'. What's the scenario we're trying to prev
Also reported here: http://dev.rubyonrails.org/ticket/6571
James Adam wrote:
> Messing around with the plugin loading mechanism (as I love to do), I
> stumbled on a $LOAD_PATH oddity and I was wondering if I'm missing the
> reasoning behind it. At the moment, plugin lib directories are added
> to
