rubigen 1.5.0 → 1.5.1

data/History.txt

@@ -1,3 +1,9 @@
+== 1.5.1 2008-12-29
+
+* Return #write_manifest which was accidently removed
+* Moved website into gh-pages branch; thus moving homepage from http://rubigen.rubforge.org -> 
+  http://drnic.github.com/rubigen
+
 == 1.5.0 2008-12-27
 
 * Preparation for integration back into Rails

data/lib/rubigen/commands.rb

@@ -56,6 +56,10 @@ module RubiGen
       def readme(*args)
       end
 
+      # Does nothing for all commands except Create.
+      def write_manifest
+      end
+      
       protected
         def current_migration_number
           Dir.glob("#{RAILS_ROOT}/#{@migration_directory}/[0-9]*_*.rb").inject(0) do |max, file_path|
@@ -374,6 +378,43 @@ module RubiGen
         end
       end
 
+      def write_manifest(relative_destination)
+        files = ([relative_destination] + Dir["#{destination_root}/**/*"])
+        files.reject! { |file| File.directory?(file) }
+        files.map! { |path| path.sub("#{destination_root}/","") }
+        files = files.uniq.sort
+
+
+        destination         = destination_path(relative_destination)
+        destination_exists  = File.exists?(destination)
+
+        # Check for and resolve file collisions.
+        if destination_exists
+          # Always recreate the Manifest (perhaps we need to give the option... like normal files)
+          choice = :force
+          logger.force(relative_destination)
+
+        # File doesn't exist so log its unbesmirched creation.
+        else
+          logger.create relative_destination
+        end
+
+        # If we're pretending, back off now.
+        return if options[:pretend]
+
+        # Write destination file with optional shebang.  Yield for content
+        # if block given so templaters may render the source file.  If a
+        # shebang is requested, replace the existing shebang or insert a
+        # new one.
+        File.open(destination, 'wb') do |dest|
+          dest.write files.join("\n")
+          dest.write "\n"
+        end
+
+        # Optionally add file to subversion
+        system("svn add #{destination}") if options[:svn]
+      end
+
       # When creating a migration, it knows to find the first available file in db/migrate and use the migration.rb template.
       def migration_template(relative_source, relative_destination, template_options = {})
         migration_directory relative_destination

data/lib/rubigen.rb

@@ -10,7 +10,7 @@ rescue LoadError
 end
 
 module RubiGen
-  VERSION = '1.5.0'
+  VERSION = '1.5.1'
 end
 
 require 'rubigen/base'

data/test/test_generator_helper.rb

@@ -14,3 +14,5 @@ end
 FileUtils.mkdir_p(APP_ROOT)
 
 require 'rubigen/helpers/generator_test_helper'
+
+FileUtils.rm_rf(File.dirname(__FILE__) + "/tmp") # seem to be issues on runcoderun with a test/tmp/... folder still

data/website/index.html

@@ -35,7 +35,7 @@
     <div class="sidebar">
       <div id="version" class="clickable" onclick='document.location = "http://rubyforge.org/projects/rubigen"; return false'>
         <p>Get Version</p>
-        <a href="http://rubyforge.org/projects/rubigen" class="numbers">1.5.0</a>
+        <a href="http://rubyforge.org/projects/rubigen" class="numbers">1.5.1</a>
       </div>
       
       <div id="twitter_search">
@@ -68,7 +68,7 @@ If you are developing a RubyGem, then you will want a different set of generator
 <p>On your development machine:</p>
 <p><pre class='syntax'><span class="ident">sudo</span> <span class="ident">gem</span> <span class="ident">install</span> <span class="ident">rubigen</span></pre></p>
 <h2>Usage</h2>
-<p>RubiGen will be normally integrated into another RubyGem, such as <code>newgem</code> or <code>merb</code> or <code>camping</code>, rather than be used on its own.</p>
+<p>RubiGen will be normally integrated into another RubyGem, such as <code>newgem</code> or <code>rails</code> or <code>camping</code>, rather than be used on its own.</p>
 <p>These frameworks might use RubiGen for two reasons:</p>
 <ol>
 	<li>To generate an initial stub for developers, e.g. <code>rails</code> generated a stub to write a Rails application. <code>newgem</code> generates a stub to write a RubyGem. <br/><br />
@@ -86,7 +86,7 @@ If you are developing a RubyGem, then you will want a different set of generator
    RubyGem development environment (as generated by <code>newgem</code>), the <code>script/generator</code><br />
    only shows <code>rubygem</code>-related generators. Rails could restrict <code>script/generator</code><br />
    to only show Rails related generators</li>
-	<li>Your framework RubyGem (e.g. <code>newgem</code> or <code>merb</code> RubyGems) needs to add <code>rubigen</code> as a <br />
+	<li>Your framework RubyGem (e.g. <code>newgem</code> or <code>rails</code> RubyGems) needs to add <code>rubigen</code> as a <br />
    dependency, so that users of your RubyGem can access the generator framework.</li>
 </ol>
 <h1>Creating generators</h1>

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification 
 name: rubigen
 version: !ruby/object:Gem::Version 
-  version: 1.5.0
+  version: 1.5.1
 platform: ruby
 authors: 
 - Dr Nic Williams
@@ -10,7 +10,7 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2008-12-27 00:00:00 +10:00
+date: 2008-12-29 00:00:00 +10:00
 default_executable: 
 dependencies: 
 - !ruby/object:Gem::Dependency