Move erector version to its own file and just include that file,

not the rest of erector, in Rakefile.  This is intended to solve some
catch-22 type problems relating to installing gems.


git-svn-id: svn+ssh://rubyforge.org/var/svn/erector/trunk@198 4b8798b9-51f2-4387-91b1-b04f834b421f

Rakefile

@@ -8,10 +8,9 @@ require './tasks/hoex.rb'  # Alex's patched version of Hoe
 
 dir = File.dirname(__FILE__)
 $: << "#{dir}/lib"
-require "erector"
-require "erector/erect"
+require "erector/version"
 
-GEM_VERSION = Erector::VERSION # defined in lib/erector.rb
+GEM_VERSION = Erector::VERSION # defined in lib/erector/version.rb
 GEM_NAME = "erector"
 
 Hoe.new(GEM_NAME, GEM_VERSION) do |hoe|

lib/erector.rb

@@ -8,12 +8,8 @@
 require "#{dir}/erector/widget"
 require "#{dir}/erector/unicode"
 require "#{dir}/erector/widgets"
+require "#{dir}/erector/version"
 if Object.const_defined?(:RAILS_ROOT)
   require "#{dir}/erector/rails"
 end
 
-##
-# Erector view framework
-module Erector
-  VERSION = "0.4.191"
-end

lib/erector/version.rb

@@ -0,0 +1,6 @@
+##
+# Erector view framework
+module Erector
+  VERSION = "0.4.191"
+end
+

web/developers.rb

@@ -44,11 +44,11 @@ def render_body
     ol do
       li "Pick a version number. For the build number run 'svn info | grep Revision'"
       li %q{Look at History.txt and make sure the release notes are up to date. Put the version number on the top line (after the "==").}
-      li "Put the version number in erector.rb as Erector::VERSION."
+      li "Put the version number in lib/erector/version.rb as Erector::VERSION."
       li %q{Check in with a comment, e.g. 'svn ci -m "release 1.2.3"'}
       li %q{Run 'rm -rf spec/rails_root' so that you don't include 3 versions of rails in the erector gem (TODO: there must be a better way to exclude these from the gem)}
       li %q{Run 'rake package' so that you can see whether the gem generation seems to work locally before proceeding to try to upload it to rubyforge (if you skip this step, the package will be generated when you run rake release)}
-      li "If you haven't done so before, run 'rubyforge setup' and 'rubyforge config' (for more details on these steps, see README.txt in the rubyforge gem"
+      li "If you haven't done so before, run 'rubyforge setup' and 'rubyforge config' (for more details on these steps, see README.txt in the rubyforge gem)"
       li "Run 'rake release VERSION=1.2.3'. (The parameter is to confirm you're releasing the version you intend to.)"
       li "Run 'rake publish_docs web publish_web' cause the docs and site need to be updated, at least with the new version number."
       li %q{Immediately go into History.txt and make a new section at the top. Since we won't yet know what the next version will be called, the new section will be noted by a single "==" at the top of the file.}