# Engines 1.2 experimental branch is now the release branch

**URL:** <https://www.ruby-forum.com/t/engines-1-2-experimental-branch-is-now-the-release-branch/81074>\
**Category:** Engines\
**Created:** [January 3, 2007, 4:40pm UTC](https://www.ruby-forum.com/t/engines-1-2-experimental-branch-is-now-the-release-branch/81074 "2007-01-03T16:40:54Z")\
**Posts on this page:** 4\
**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:** [January 3, 2007, 4:40pm UTC](https://www.ruby-forum.com/t/engines-1-2-experimental-branch-is-now-the-release-branch/81074/1 "2007-01-03T16:40:54Z")

</div>

… which means things are going to break if your running the Rails  
1.2 release candidate. You can find the new 1.2 release branch here:

[http://svn.rails-engines.org/engines/branches/rb\_1.2](http://svn.rails-engines.org/engines/branches/rb_1.2)

If you _must_ maintain compatibility, use the following SVN URL to  
access to old 1.2 release:

[http://svn.rails-engines.org/engines/branches/unsupported/old\_1.2](http://svn.rails-engines.org/engines/branches/unsupported/old_1.2)

It’s worth mentioning now that the current releases of the login and  
user engines will also not work with the new 1.2 branch for the  
moment. While I’ve tried to avoid change wherever possible, to fit  
better with Rails 1.2 the next release of Engines is a different beast

- hopefully the advantages of the new codebase outweighs the hiccup of  
bringing your plugins into sync.

Developers, please examine the code to find out how to make your  
plugins compatible; I’ll be posting more in the very near future  
describing the changes in detail - feedback gratefully requested!

James

---

<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:** [January 3, 2007, 6:57pm UTC](https://www.ruby-forum.com/t/engines-1-2-experimental-branch-is-now-the-release-branch/81074/2 "2007-01-03T18:57:51Z")

</div>

Hi James,

thanks a lot for your reply. Great Work!

TIA,

Daniel

---

<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:** [January 19, 2007, 4:30pm UTC](https://www.ruby-forum.com/t/engines-1-2-experimental-branch-is-now-the-release-branch/81074/3 "2007-01-19T16:30:47Z")

</div>

Hi Michael,

This was a result of the fact that plugins can be ‘enginized’ as part  
of the plugin loading process now, which occurs before routing is  
started up. Previously this wasn’t an issue because Engines.start was  
called after routing was configured. There’s a fix in the release  
branch; see [http://dev.rails-engines.org/tickets/258](http://dev.rails-engines.org/tickets/258) for more details.

Documentation is forthcoming; for the moment, your best bet is to get  
familiar with the source code. I’m posting details about the new  
behaviours/features at [http://rails-engines.org](http://rails-engines.org) and  
[http://interblah.net](http://interblah.net).

- James

---

<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:** [January 6, 2007, 7:30pm UTC](https://www.ruby-forum.com/t/engines-1-2-experimental-branch-is-now-the-release-branch/81074/4 "2007-01-06T19:30:47Z")

</div>

On Jan 3, 2007, at 7:39 AM, James A. wrote:

> … which means things are going to break if your running the Rails  
> 1.2 release candidate. You can find the new 1.2 release branch here:
> 
> [http://svn.rails-engines.org/engines/branches/rb\_1.2](http://svn.rails-engines.org/engines/branches/rb_1.2)

James- I grabbed the 1.2 engines plugin and Edge Rails, but I’m not  
sure where to look for Docs related to the new versions.

I have a simple plugin that I want to setup to work with Engines or  
the appable\_plugin (not sure if this one does views). The  
appable\_plugin works if I manually put the views in place, but with  
Engines all I get are routing errors. I’m sure I’m missing something  
simple, but I’m not sure where to look with all the new changes.

Thanks in advance for your time.

Michael-