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 <[EMAIL PROTECTED]> wrote: > What about auto-detecting what version of Rails it is running? :) > > -Nb > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Nathaniel S. H. Brown http://nshb.net > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On > > Behalf Of James Adam > > Sent: February 13, 2006 5:16 PM > > To: [email protected]; > > [email protected] > > Subject: [Engine-users] Engines and Edge Rails > > > > 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 > > > > 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 > > > > Thanks in advance for your help and patience, I'll post again > > in a second about how to test the Engines plugin. > > > > James > > > > -- > > * J * > > ~ > > _______________________________________________ > > engine-users mailing list > > [email protected] > > http://lists.rails-engines.org/listinfo.cgi/engine-users-rails > > -engines.org > > > > _______________________________________________ > engine-users mailing list > [email protected] > http://lists.rails-engines.org/listinfo.cgi/engine-users-rails-engines.org > -- * J * ~ _______________________________________________ engine-users mailing list [email protected] http://lists.rails-engines.org/listinfo.cgi/engine-users-rails-engines.org
