<?xml version="1.0" encoding="UTF-8"?>
<commit>
  <added type="array"/>
  <modified type="array">
    <modified>
      <diff>@@ -1,4 +1,4 @@
-= 2.0 - (ANOTHER) MASSIVE INTERNAL REFACTORING
+= 2.0.0 - (ANOTHER) MASSIVE INTERNAL REFACTORING
 
 * Engines now conforms to the new plugin loading mechanism, delegating plugin load order and lots of other things to Rails itself.
 </diff>
      <filename>CHANGELOG</filename>
    </modified>
    <modified>
      <diff>@@ -4,15 +4,14 @@ For more information, see http://rails-engines.org
 
 = Using the plugin
 
-With engines 1.2, no extra configuration in environment.rb is required. Having the plugin installed will automatically enable sharing of code within &lt;tt&gt;plugin/app/&lt;/tt&gt; directories. Developers should be aware that the &lt;tt&gt;config.plugins&lt;/tt&gt; parameter can be used to control plugin load order, if this is important for your application.
+Once you've installed the engines plugin, you'll need to add a single line to the top of config/environment.rb:
 
-=== config.plugins
+  require File.join(File.dirname(__FILE__), '../vendor/plugins/engines/boot')
+  
+You should add this line just below the require for Rails' own boot.rb file. This will enabled the enhanced plugin loading mechanism automatically for you (i.e. you don't need to set config.plugin_loader manually).
 
-With Rails 1.2, the &lt;tt&gt;config.plugins&lt;/tt&gt; list can be used to specify the order in which plugins are loaded. It's recommended (although not required) that you load the engines plugin first, and any other plugins later. The engines plugin enhances Rails' processing of &lt;tt&gt;config.plugins&lt;/tt&gt; for occasions where you only care about the order of a small selection of your application's plugins. For instance, if you want to load +engines+ first, and anything else afterwards, then
+With that aside, you're now ready to start using more powerful plugins in your application. Read on to find out more about what the engines plugin enables.
 
-  config.plugins = [&quot;engines&quot;, &quot;*&quot;]
-  
-will ensure that engines is loaded first, and everything else (in whatever order Rails chooses) afterwards.
 
 == Better plugins
 </diff>
      <filename>README</filename>
    </modified>
    <modified>
      <diff>@@ -17,7 +17,7 @@ end
 desc 'Run the engine plugin tests within their test harness'
 task :cruise do
   # checkout the project into a temporary directory
-  version = &quot;rails_1.2&quot;
+  version = &quot;rails_2.0&quot;
   test_dir = &quot;#{Dir.tmpdir}/engines_plugin_#{version}_test&quot;
   puts &quot;Checking out test harness for #{version} into #{test_dir}&quot;
   `svn co http://svn.rails-engines.org/test/engines/#{version} #{test_dir}`</diff>
      <filename>Rakefile</filename>
    </modified>
    <modified>
      <diff>@@ -4,4 +4,4 @@ homepage: http://www.rails-engines.org
 summary: Enhances the plugin mechanism to perform more flexible sharing
 description: The Rails Engines plugin allows the sharing of almost any type of code or asset that you could use in a Rails application, including controllers, models, stylesheets, and views.
 license: MIT
-version: 1.2.0
\ No newline at end of file
+version: 2.0.0-RC1
\ No newline at end of file</diff>
      <filename>about.yml</filename>
    </modified>
  </modified>
  <removed type="array"/>
  <parents type="array">
    <parent>
      <id>c2158488a9a8477c39ecf4a1281e9b451a483426</id>
    </parent>
  </parents>
  <author>
    <name>lazyatom</name>
    <email>lazyatom@61cc408d-6c04-0410-aff7-b3608aa29ce9</email>
  </author>
  <url>http://github.com/yar/engines/commit/64ea89d6510319cde045d3975b7626dc4ecd4736</url>
  <id>64ea89d6510319cde045d3975b7626dc4ecd4736</id>
  <committed-date>2007-12-09T14:31:26-08:00</committed-date>
  <authored-date>2007-12-09T14:31:26-08:00</authored-date>
  <message>Updated some documentation and other misc things for Rails 2.0

git-svn-id: http://svn.rails-engines.org/engines/trunk@661 61cc408d-6c04-0410-aff7-b3608aa29ce9</message>
  <tree>715639cfaac8564f65918929a2e761cb6b954a38</tree>
  <committer>
    <name>lazyatom</name>
    <email>lazyatom@61cc408d-6c04-0410-aff7-b3608aa29ce9</email>
  </committer>
</commit>
