# 1.2.3 Upgrade from 1.1.6 dependencies issues

**URL:** <https://www.ruby-forum.com/t/1-2-3-upgrade-from-1-1-6-dependencies-issues/114642>\
**Category:** Rails\
**Created:** [September 17, 2007, 1:23pm UTC](https://www.ruby-forum.com/t/1-2-3-upgrade-from-1-1-6-dependencies-issues/114642 "2007-09-17T13:23:29Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![will](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/w/90ced4/32.png) [@will](https://www.ruby-forum.com/u/will)\
**Post date:** [September 17, 2007, 1:23pm UTC](https://www.ruby-forum.com/t/1-2-3-upgrade-from-1-1-6-dependencies-issues/114642/1 "2007-09-17T13:23:29Z")

</div>

Is there a tutorial or good example of what to look for for  
dependencies issues in a Rails application. I am working with a large  
Rails application that is in the process of being ported to 1.2.3 and  
could use ideas. I have added

require ‘exception\_notifier\_helper’  
require ‘exception\_notifier’  
require ‘active\_support’  
require ‘active\_record’  
require ‘action\_mailer’  
require ‘action\_pack’  
require ‘login\_engine’  
require ‘datebox\_engine’

to environment.rb on startup?

Will I need to add references to all my Models/Controllers into the  
applications since Auto-loading is fixed/broken???

Auto-loading

We’ve fixed a bug that allowed libraries from Ruby’s standard library  
to be auto-loaded on reference. Before, if you merely reference the  
Pathname constant, we’d autoload pathname.rb. No more, you’ll need to  
manually require ‘pathname’ now.

We’ve also improved the handling of module loading, which means that a  
reference for Accounting::Subscription will look for app/models/  
accounting/subscription.rb. At the same time, that means that merely  
referencing Subscription will not look for subscription.rb in any  
subdir of app/models. Only app/models/subscription.rb will be tried.  
If you for some reason depended on this, you can still get it back by  
adding app/models/accounting to config.load\_paths in config/  
environment.rb.

---

<div class="post-metadata">

**Author:** ![will](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/w/90ced4/32.png) [@will](https://www.ruby-forum.com/u/will)\
**Post date:** [September 17, 2007, 1:24pm UTC](https://www.ruby-forum.com/t/1-2-3-upgrade-from-1-1-6-dependencies-issues/114642/2 "2007-09-17T13:24:14Z")

</div>

For starters, although Engines is supported under 1.2.3, Login\_engine is  
not. Im having to go through the process right now but the issues im  
having  
are related to the way it was originally coded (as some of the people  
from  
LSRC could probably attest to).  
Only advice I can give is put this in the init section in the  
environment.rbfile.

config.after\_initialize do  
Dependencies.log\_activity = true  
end

On 9/14/07, Will [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> require ‘active\_record’  
> Auto-loading  
> subdir of app/models. Only app/models/subscription.rb will be tried.  
> If you for some reason depended on this, you can still get it back by  
> adding app/models/accounting to config.load\_paths in config/  
> environment.rb.
> 
> >

–  
Richard J Hancock  
Developer/System A.