# Engines and Edge Rails

**URL:** <https://www.ruby-forum.com/t/engines-and-edge-rails/67583>\
**Category:** Engines\
**Created:** [February 14, 2006, 2:17am UTC](https://www.ruby-forum.com/t/engines-and-edge-rails/67583 "2006-02-14T02:17:53Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![nitr0z](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/ba9def/32.png) [@nitr0z](https://www.ruby-forum.com/u/nitr0z)\
**Post date:** [February 14, 2006, 2:17am UTC](https://www.ruby-forum.com/t/engines-and-edge-rails/67583/1 "2006-02-14T02:17:53Z")

</div>

Hi all,

- /branches/edge is retiring; it will be removed very soon.
- /trunk is the new head of development, and it’s ‘Universal’
- → Engines.config(:edge, true) to switch on Edge Rails compatibility
- → \*\*\*\*\*\*\*\*\*please submit patches!!! \*\*\*\*\*\*\*\*\*\*

… As some of you are aware, the Rails core team are currently  
overhauling their dependency mechanism to allow better use of modules  
and ‘namespacing’ of your code. This is going to have an impact on the  
Engines plugin, since it fundamentally works by enhancing that  
particular functionality. If you want/need to use Edge Rails, you  
should use the version of the Engines plugin now located in the trunk  
of the repository:

[http://opensvn.csie.org/rails\_engines/engines/trunk](http://opensvn.csie.org/rails_engines/engines/trunk)

To reiterate, if you are currently using the /branches/edge plugin,  
_please_ switch to the /trunk. If this causes you issues, please spend  
some time tracking down the source so we can fix the bug in /trunk. I  
have merged all the development from the 1.0 release branch into this  
path, so you’ll be getting all of the features and fixes from that  
branch, which should more than make it worthwhile.

The /trunk plugin is ‘universal’, in that it should be able to operate  
with both Edge Rails and the 1.0 release. To ‘activate’ the Edge  
functionality, add the line:

Engines.config :edge, true

to your environment.rb file (it probably doesn’t matter where, but I’d  
add it as the first line after “# Include your application  
configuration below” if I were you). By toggling this configuration  
value you can switch on and off the Edge rails-compatible methods. If  
you don’t include this line, I can pretty much guarantee that you’ll  
have issues in Edge Rails.

IMPORTANT NOTE! Since my time is somewhat limited at the moment, I’m  
relying on the submission of detailed bug reports and even more  
helpfully patches to the dependency mechanisms so we can maintain  
compatibility with Rails as it approaches 1.1. The Rails Engines Trac  
site is the place to check for existing tickets if you have an issue,  
or raise a new ticket if you cannot find your issue already on the  
site:

[https://opensvn.csie.org/traccgi/rails\_engines/trac.cgi/report/1](https://opensvn.csie.org/traccgi/rails_engines/trac.cgi/report/1)

Thanks in advance for your help and patience, I’ll post again in a  
second about how to test the Engines plugin.

James

–

- J \*  
~

---

<div class="post-metadata">

**Author:** ![nitr0z](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/ba9def/32.png) [@nitr0z](https://www.ruby-forum.com/u/nitr0z)\
**Post date:** [February 14, 2006, 4:26am UTC](https://www.ruby-forum.com/t/engines-and-edge-rails/67583/2 "2006-02-14T04:26:34Z")

</div>

What about auto-detecting what version of Rails it is running? 🙂

-Nb

```auto
 Nathaniel S. H. Brown http://nshb.net

```

---

<div class="post-metadata">

**Author:** ![nitr0z](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/ba9def/32.png) [@nitr0z](https://www.ruby-forum.com/u/nitr0z)\
**Post date:** [February 14, 2006, 9:40am UTC](https://www.ruby-forum.com/t/engines-and-edge-rails/67583/3 "2006-02-14T09:40:16Z")

</div>

It actually tries to do that, but edge rails currently reports itself  
as 1.0.0, so that wouldn’t work at the moment…

On 2/14/06, Nathaniel S. H. Brown [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> > From: removed\_email\_address@domain.invalid
> > 
> > - /trunk is the new head of development, and it’s ‘Universal’  
> > functionality. If you want/need to use Edge Rails, you should  
> > of the features and fixes from that branch, which should more  
> > application configuration below" if I were you). By toggling  
> > if you cannot find your issue already on the
> > - J \*  
> > removed\_email\_address@domain.invalid  
> > [http://lists.rails-engines.org/listinfo.cgi/engine-users-rails-engines.org](http://lists.rails-engines.org/listinfo.cgi/engine-users-rails-engines.org)

–

- J \*  
~