noe 1.1.0 → 1.2.0

data/templates/ruby/src/tasks/debug_mail.rake

@@ -0,0 +1,77 @@
+# Installs a rake task for debuging the announcement mail.
+#
+# This file installs the 'rake debug_mail' that flushes an announcement mail
+# for your library on the standard output. It is automatically generated 
+# by Noe from your .noespec file, and should therefore be configured there, 
+# under the variables/rake_tasks/debug_mail entry, as illustrated below:
+#
+# variables:
+#   rake_tasks:
+#     debug_mail:
+#       rx_changelog_sections: /^#/
+#       nb_changelog_sections: 1
+#       ...
+#
+# If you have specific needs requiring manual intervention on this file, 
+# don't forget to set safe-override to false in your noe specification:
+# 
+# template-info:
+#   manifest:
+#     tasks/debug_mail.rake:
+#       safe-override: false
+#
+# The mail template used can be found in debug_mail.txt. That file may be
+# changed to tune the mail you want to send. If you do so, don't forget to
+# add a manifest entry in your .noespec file to avoid overriding you 
+# changes. The mail template uses wlang, with parentheses for block 
+# delimiters.
+#
+# template-info:
+#   manifest:
+#     tasks/debug_mail.txt:
+#       safe-override: false
+#
+begin
+  require 'wlang'
+  require 'yaml'
+  
+  task :debug_mail do 
+    # Check that a .noespec file exists
+    noespec_file = File.expand_path('../../!{lower}.noespec', __FILE__)
+    unless File.exists?(noespec_file)
+      raise "Unable to find .noespec project file, sorry."
+    end
+    
+    # Load it as well as variables and options
+    noespec = YAML::load(File.read(noespec_file))
+    vars = noespec['variables'] || {}
+
+    # Changes are taken from CHANGELOG 
+    logs = Dir[File.expand_path("../../CHANGELOG.*", __FILE__)]
+    unless logs.size == 1
+      abort "Unable to find a changelog file"
+    end
+
+    # Load interesting changesets
+    changes, end_found = [], 0
+    File.readlines(logs.first).select{|line|
+      if line =~ !{rake_tasks.debug_mail.rx_changelog_sections}
+        break if end_found >= +{rake_tasks.debug_mail.nb_changelog_sections}
+        end_found += 1
+      end
+      changes << line
+    }
+    vars['changes'] = changes.join
+    
+    # WLang template
+    template = File.expand_path('../debug_mail.txt', __FILE__)
+    
+    # Let's go!
+    $stdout << WLang::file_instantiate(template, vars, "wlang/active-text")
+  end
+
+rescue LoadError 
+  task :debug_mail do
+    abort "wlang is not available. Try 'gem install wlang'"
+  end
+end

data/templates/ruby/src/tasks/debug_mail.txt

@@ -0,0 +1,13 @@
+Subject: [ANN] !{lower} !{version} Released
+
+!{lower} version !{version} has been released!
+
+!{summary}
+
+*{links as l}{* <!{l}>}{!{"\n"}}
+
+!{description}
+
+Changes:
+
+!{changes}

data/templates/ruby/src/tasks/gem.rake

@@ -1,4 +1,28 @@
-# Install .gem project packaging
+# Installs rake tasks for gemming and packaging
+#
+# This file installs the 'rake package', 'rake gem' tasks and associates 
+# (clobber_package, repackage, ...). It is automatically generated by Noe 
+# from your .noespec file, and should therefore be configured there, under 
+# the variables/rake_tasks/gem entry, as illustrated below:
+#
+# variables:
+#   rake_tasks:
+#     gem:
+#       package_dir: pkg
+#       need_tar: false
+#       need_tar_gz: false
+#       need_tar_bz2: false
+#       need_zip: false
+#       ...
+#
+# If you have specific needs requiring manual intervention on this file, 
+# don't forget to set safe-override to false in your noe specification:
+# 
+# template-info:
+#   manifest:
+#     tasks/gem.rake:
+#       safe-override: false
+#
 begin
   require 'rubygems/package_task'
   Gem::PackageTask.new($gemspec) do |t|
@@ -10,28 +34,28 @@ begin
     t.version = $gemspec.version
     
     # Directory used to store the package files
-    t.package_dir = 'pkg'
+    t.package_dir = +{rake_tasks.gem.package_dir}
     
     # True if a gzipped tar file (tgz) should be produced
-    t.need_tar = false
+    t.need_tar = +{rake_tasks.gem.need_tar}
     
     # True if a gzipped tar file (tar.gz) should be produced
-    t.need_tar_gz = true
+    t.need_tar_gz = +{rake_tasks.gem.need_tar_gz}
     
     # True if a bzip2'd tar file (tar.bz2) should be produced
-    t.need_tar_bz2 = false
+    t.need_tar_bz2 = +{rake_tasks.gem.need_tar_bz2}
     
     # True if a zip file should be produced (default is false)
-    t.need_zip = true
+    t.need_zip = +{rake_tasks.gem.need_zip}
     
     # List of files to be included in the package.
     t.package_files = $gemspec.files
     
     # Tar command for gzipped or bzip2ed archives.
-    t.tar_command = 'tar'
+    t.tar_command = +{rake_tasks.gem.tar_command}
     
     # Zip command for zipped archives.
-    t.zip_command = 'zip'
+    t.zip_command = +{rake_tasks.gem.zip_command}
 
   end
 rescue LoadError

data/templates/ruby/src/tasks/spec_test.rake

@@ -1,55 +1,73 @@
+# Installs a rake task for for running examples written using rspec.
 #
-# Install a rake task for running examples written using rspec.
+# This file installs the 'rake spec_test' (aliased as 'rake spec') as well as
+# extends 'rake test' to run spec tests, if any. It is automatically generated 
+# by Noe from your .noespec file, and should therefore be configured there, 
+# under the variables/rake_tasks/spec_test entry, as illustrated below:
 #
-# More information about rspec: http://relishapp.com/rspec
-# This file has been written to conform to RSpec v2.4.0
+# variables:
+#   rake_tasks:
+#     spec_test:
+#       pattern: spec/**/*_spec.rb
+#       verbose: true
+#       rspec_opts: [--color, --backtrace]
+#       ...
+#
+# If you have specific needs requiring manual intervention on this file, 
+# don't forget to set safe-override to false in your noe specification:
+# 
+# template-info:
+#   manifest:
+#     tasks/spec_test.rake:
+#       safe-override: false
+#
+# This file has been written to conform to RSpec v2.4.0. More information about 
+# rspec and options of the rake task defined below can be found on 
+# http://relishapp.com/rspec
 #
 begin
   require "rspec/core/rake_task"
   desc "Run RSpec code examples"
   RSpec::Core::RakeTask.new(:spec_test) do |t|
     # Glob pattern to match files.
-    t.pattern = 'spec/**/*_spec.rb'
+    t.pattern = +{rake_tasks.spec_test.pattern}
 
     # By default, if there is a Gemfile, the generated command will include
     # 'bundle exec'. Set this to true to ignore the presence of a Gemfile, 
     # and not add 'bundle exec' to the command.
-    t.skip_bundler = false
+    t.skip_bundler = +{rake_tasks.spec_test.skip_bundler}
 
     # Name of Gemfile to use
-    t.gemfile = 'Gemfile'
+    t.gemfile = +{rake_tasks.spec_test.gemfile}
 
     # Whether or not to fail Rake when an error occurs (typically when 
     # examples fail).
-    t.fail_on_error = true
+    t.fail_on_error = +{rake_tasks.spec_test.fail_on_error}
 
     # A message to print to stderr when there are failures.
-    t.failure_message = nil
+    t.failure_message = +{rake_tasks.spec_test.failure_message}
 
     # Use verbose output. If this is set to true, the task will print the
     # executed spec command to stdout.
-    t.verbose = true
+    t.verbose = +{rake_tasks.spec_test.verbose}
 
     # Use rcov for code coverage?
-    t.rcov = false
+    t.rcov = +{rake_tasks.spec_test.rcov}
 
     # Path to rcov.
-    t.rcov_path = 'rcov'
+    t.rcov_path = +{rake_tasks.spec_test.rcov_path}
 
-    # Command line options to pass to rcov.
-    # See 'rcov --help' about this
-    t.rcov_opts = %w{}
+    # Command line options to pass to rcov. See 'rcov --help' about this
+    t.rcov_opts = +{rake_tasks.spec_test.rcov_opts}
 
-    # Command line options to pass to ruby.
-    # See 'ruby --help' about this 
-    t.ruby_opts = %w{}
+    # Command line options to pass to ruby. See 'ruby --help' about this 
+    t.ruby_opts = +{rake_tasks.spec_test.ruby_opts}
 
     # Path to rspec
-    t.rspec_path = 'rspec'
+    t.rspec_path = +{rake_tasks.spec_test.rspec_path}
 
-    # Command line options to pass to rspec.
-    # See 'rspec --help' about this
-    t.rspec_opts = %w{--color --backtrace}
+    # Command line options to pass to rspec. See 'rspec --help' about this
+    t.rspec_opts = +{rake_tasks.spec_test.rspec_opts}
   end
 rescue LoadError => ex
   task :spec_test do

data/templates/ruby/src/tasks/unit_test.rake

@@ -1,8 +1,28 @@
+# Installs a rake task for for running unit tests.
 #
-# Install a rake task for running examples written using rspec.
+# This file installs the 'rake unit_test' and extends 'rake test' to run unit 
+# tests, if any. It is automatically generated by Noe from your .noespec file, 
+# and should therefore be configured there, under the variables/rake_tasks/unit_test 
+# entry, as illustrated below:
 #
-# More information about rspec: http://relishapp.com/rspec
-# This file has been written to conform to RSpec v2.4.0
+# variables:
+#   rake_tasks:
+#     unit_test:
+#       pattern: test/test*.rb
+#       verbose: false
+#       warning: false
+#       ...
+#
+# If you have specific needs requiring manual intervention on this file, 
+# don't forget to set safe-override to false in your noe specification:
+# 
+# template-info:
+#   manifest:
+#     tasks/unit_test.rake:
+#       safe-override: false
+#
+# More info about the TestTask and its options can be found on 
+# http://rake.rubyforge.org/classes/Rake/TestTask.html
 #
 begin
   desc "Lauches unit tests"
@@ -11,21 +31,21 @@ begin
 
     # List of directories to added to $LOAD_PATH before running the
     # tests. (default is 'lib')
-    t.libs = %w{ lib }
+    t.libs = +{rake_tasks.unit_test.libs}
 
     # True if verbose test output desired. (default is false)
-    t.verbose = false
+    t.verbose = +{rake_tasks.unit_test.verbose}
 
     # Test options passed to the test suite.  An explicit TESTOPTS=opts 
     # on the command line will override this. (default is NONE)
-    t.options = []
+    t.options = +{rake_tasks.unit_test.options}
 
     # Request that the tests be run with the warning flag set.
     # E.g. warning=true implies "ruby -w" used to run the tests.
-    t.warning = false
+    t.warning = +{rake_tasks.unit_test.warning}
 
     # Glob pattern to match test files. (default is 'test/test*.rb')
-    t.pattern = 'test/test*.rb'
+    t.pattern = +{rake_tasks.unit_test.pattern}
 
     # Style of test loader to use.  Options are:
     #
@@ -33,17 +53,17 @@ begin
     # * :testrb -- Ruby provided test loading script.
     # * :direct -- Load tests using command line loader.
     # 
-    t.loader = :rake
+    t.loader = +{rake_tasks.unit_test.loader}
 
     # Array of commandline options to pass to ruby when running test 
     # loader.
-    t.ruby_opts = []
+    t.ruby_opts = +{rake_tasks.unit_test.ruby_opts}
 
     # Explicitly define the list of test files to be included in a
     # test.  +list+ is expected to be an array of file names (a
     # FileList is acceptable).  If both +pattern+ and +test_files+ are
     # used, then the list of test files is the union of the two.
-    t.test_files = nil
+    t.test_files = +{rake_tasks.unit_test.test_files}
 
   end
 rescue LoadError => ex

data/templates/ruby/src/tasks/yard.rake

@@ -1,22 +1,37 @@
+# Installs a rake task to generate API documentation using yard.
+#
+# This file installs the 'rake yard' task. It is automatically generated by Noe from 
+# your .noespec file, and should therefore be configured there, under the 
+# variables/rake_tasks/yard entry, as illustrated below:
+#
+# variables:
+#   rake_tasks:
+#     yard:
+#       files: lib/**/*.rb
+#       options: []
+#       ...
+#
+# If you have specific needs requiring manual intervention on this file, 
+# don't forget to set safe-override to false in your noe specification:
 # 
-# Install a rake task to generate API documentation using
-# yard.
+# template-info:
+#   manifest:
+#     tasks/yard.rake:
+#       safe-override: false
 #
-# More information about yard: http://yardoc.org/
-# This file has been written to conform to yard v0.6.4
+# This file has been written to conform to yard v0.6.4. More information about 
+# yard and the rake task installed below can be found on http://yardoc.org/
 #
-# About project documentation
 begin
   require "yard"
   desc "Generate yard documentation"
   YARD::Rake::YardocTask.new(:yard) do |t|
-    # Array of options passed to the commandline utility
-    # See 'yardoc --help' about this
-    t.options = %w{--output-dir doc/api - README.md CHANGELOG.md LICENCE.md}
+    # Array of options passed to yardoc commandline. See 'yardoc --help' about this
+    t.options = +{rake_tasks.yard.options}
     
     # Array of ruby source files (and any extra documentation files 
     # separated by '-')
-    t.files = ['lib/**/*.rb']
+    t.files = +{rake_tasks.yard.files}
     
     # A proc to call before running the task
     # t.before = proc{ }

metadata

@@ -1,13 +1,13 @@
 --- !ruby/object:Gem::Specification 
 name: noe
 version: !ruby/object:Gem::Version 
-  hash: 19
+  hash: 31
   prerelease: 
   segments: 
   - 1
-  - 1
+  - 2
   - 0
-  version: 1.1.0
+  version: 1.2.0
 platform: ruby
 authors: 
 - Bernard Lambeau
@@ -15,7 +15,7 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2011-01-15 00:00:00 +01:00
+date: 2011-01-17 00:00:00 +01:00
 default_executable: 
 dependencies: 
 - !ruby/object:Gem::Dependency 
@@ -100,24 +100,40 @@ dependencies:
 - !ruby/object:Gem::Dependency 
   prerelease: false
   name: wlang
-  type: :runtime
+  type: :development
   version_requirements: &id006 !ruby/object:Gem::Requirement 
     none: false
     requirements: 
     - - ~>
       - !ruby/object:Gem::Version 
-        hash: 55
+        hash: 53
         segments: 
         - 0
         - 10
-        - 0
-        version: 0.10.0
+        - 1
+        version: 0.10.1
   requirement: *id006
 - !ruby/object:Gem::Dependency 
   prerelease: false
-  name: quickl
+  name: wlang
   type: :runtime
   version_requirements: &id007 !ruby/object:Gem::Requirement 
+    none: false
+    requirements: 
+    - - ~>
+      - !ruby/object:Gem::Version 
+        hash: 53
+        segments: 
+        - 0
+        - 10
+        - 1
+        version: 0.10.1
+  requirement: *id007
+- !ruby/object:Gem::Dependency 
+  prerelease: false
+  name: quickl
+  type: :runtime
+  version_requirements: &id008 !ruby/object:Gem::Requirement 
     none: false
     requirements: 
     - - ~>
@@ -128,12 +144,12 @@ dependencies:
         - 2
         - 0
         version: 0.2.0
-  requirement: *id007
+  requirement: *id008
 - !ruby/object:Gem::Dependency 
   prerelease: false
   name: highline
   type: :runtime
-  version_requirements: &id008 !ruby/object:Gem::Requirement 
+  version_requirements: &id009 !ruby/object:Gem::Requirement 
     none: false
     requirements: 
     - - ~>
@@ -144,192 +160,8 @@ dependencies:
         - 6
         - 0
         version: 1.6.0
-  requirement: *id008
-description: |
-  # Noe - A simple and extensible project generator
-  
-  Noe is a tool that generates projects from predefined skeletons (aka project/application 
-  templates). Skeletons are designed for building specific products (a ruby library, a static 
-  or dynamic web site, ...). Noe instantiates them and helps you maintaining your product 
-  via meta-information provided by a .noespec yaml file. 
-  
-  Noe comes bundled with a skeleton for creating and maintaining a ruby gem. This skeleton 
-  is written and maintained to follow ruby best practices and may also be tuned for your own 
-  needs. Read more about it and related projects as well as the underlying philosophy in the 
-  sections below.
-  
-  ## Getting started
-  
-      [sudo] gem install noe
-      [noe --help]
-      [noe help install]
-      noe install 
-      
-  Have a loot at ~/.noerc and ~/.noe for configuration and a default ruby template. To 
-  instantiate a ruby project simply execute the following commands in turn:
-  
-      # Given a template ruby under ~/.noe/ruby, install by default
-      noe prepare --template=ruby foo
-      cd foo
-    
-      # Edit the template configuration foo/foo.noespec
-      edit foo/foo.noespec
-    
-      # Launch template instantiation
-      noe go
-    
-  That's it! But also have a look at 'noe help prepare' and 'not help go' for additional
-  options.
-  
-  ## Philosophy
-  
-  Noe is designed to follow a certain number of good principles and helps you following 
-  them as well.
-  
-  ### Separation of concerns
-  
-  Noe maintains a strong separation of concerns. In particular one has to make the distinction 
-  between a) Noe itself, b) a skeleton and c) an instantiated product. This fact has two 
-  main consequences:
-  
-  * Noe itself **is not dedicated to specific products** (like a ruby library). Even if Noe 
-    comes bundled with a default skeleton for ruby projects, writing skeletons for something
-    else should not be a problem. In other words, Noe itself is agnostic: the semantics of 
-    generated products is the secret of the skeleton, under the responsibility of it's 
-    maintainer. 
-  
-  * Noe **should not be a runtime dependency** of the product. Good skeletons maintain this 
-    separation. As an example the default ruby skeleton is strictly independent of Noe itself.
-    Principles discussed below explain why this is important.
-  
-  ### Master the tools YOU use
-  
-  The separation of concerns described previously also drives what you have to learn and what
-  tools you have to master:
-  
-  * As an ordinary Noe user (vs. skeleton maintainer) and because Noe itself (unlike skeletons
-    is project agnostic, you only have to know **basic Noe commands** (see 'noe --help') and 
-    should never have to study Noe's API and internals. In contrast, you have to **master the 
-    tools and best practices of your product's ecosystem**. A good skeleton should help you 
-    along this task. As an example, the default ruby skeleton is fully documented to help you 
-    gaining understanding of ***rake*, *spec*, *yard*, *bundler*** and so on but **not noe 
-    itself**. 
-    
-  * This explains why Noe itself is not a runtime dependency. Using a particular skeleton 
-    already means learning a lot, at least in the long run (see the section about Magic below). 
-    Noe avoids interfering with generated products to avoid making the learning curve even 
-    worse.
-  
-  * Being a skeleton creator/maintainer is another story of course. To write a skeleton you'll 
-    also have to learn **Noe's API and internals**. To write a good/reusable one, you'll 
-    certainly have to **master the full ecosystem and best practices of the targetted product**, 
-    which is a good opportunity for learning and sharing it!
-  
-  ### Magic Only If Flexible
-  
-  "Don't Repeat Yourself" and "Convention over Configuration" are certainly good principles. 
-  However tuning, configuration and options exist, are useful and should certainly not be 
-  hidden to the user. Instead configuration and options should come with default values, 
-  and should be fully documented. Providing magic is great if there is a user-centric way 
-  (in contrast to a developer one) of understanding and controlling the magic and underlying 
-  assumptions.
-  
-  As an example, the default ruby template comes with some magic: you can create a project 
-  and immediately invoke 'rake test', 'rake yard', ... and not investigating further. You 
-  can also have a look at the _tasks_ folder to understand and control the rake tasks that 
-  your project will use... In fact, you **must** investigate: the generated product is yours, 
-  not mine and YOU have to master your build chain!
-    
-  ## Ruby skeleton and Related projects
-  
-  Noe is inspired by existing projects, mostly from the ruby community. In particular, the 
-  default ruby template has been heavily influenced by the projects below as well as feedback 
-  of their authors:
-  
-  * [hoe](http://seattlerb.rubyforge.org/hoe/), Ryan Davis and Eric Hodel 
-  * [echoe](https://github.com/fauna/echoe), Evan Weaver 
-  * [bones](https://github.com/TwP/bones), Tim Pease
-  
-  These projects help you generating and maintaining ruby projects (generally gem libraries, 
-  in fact). All provide powerful tools that supports you along the different steps of your 
-  ruby software lifecycle (creating, testing, releasing, announcing, and so on.). They mostly
-  differ in the way you can tune/configure the generated project for specific needs. 
-  
-  These projects differ from the Ruby skeleton proposed by Noe in that they use a control 
-  approach (rake tasks installed in your project via a development/runtime dependency) while 
-  Noe uses a generative approach (the generated ruby project and rake tasks do not depend on 
-  Noe at all).
-  
-  You'll find more information about the Noe's ruby skeleton in it's own 
-  [README](https://github.com/blambeau/noe/blob/master/templates/ruby/README.md).
-  
-  ## Short guide for template maintainers
-  
-  Under ~/.noe, a valid template folder (say xxx) has the following structure
-  
-      xxx                         # Template name
-        README(.md|.txt|...)      #   Information about the template and it's usage
-        CHANGELOG(.md|.txt|...)   #   Change information
-        noespec.yaml              #   Template specification
-        src                       #   Source folder, contains files to be instantiated
-          ...                     #     [everything that will be instantiated]
-  
-  ### noespec.yaml
-  
-  The noespec.yaml file of a template is used to formally describe the template. When a 
-  project (say foo) is created (see 'noe prepare') using a template (say ruby) the file 
-  ~/.noe/ruby/noespec.yaml is used to generate foo/foo.noespec. The later is then used 
-  by 'noe go' to instantiate the project.
-  
-  The noespec.yaml file should ressemble something like this:
-  
-      # DO NOT TOUCH 'name' entry and specify the other
-      template-info:
-        name: !{template_name}
-        summary: ...
-        description: ...
-        version: ...
-        author: ...
-  
-      #
-      # The following is a hash of template-related variables. They are
-      # used to provide dynamic file names and instantiate file contents.
-      #
-      # Current version of Noe only supports variable names matching /[a-z]+/
-      #
-      variables:
-        ...
-  
-  Have a look at ~/.noe/ruby/noespec.yaml and ~/.noe/ruby/src for an example.
-  
-  ### Instantiation process
-  
-  The instantiation process is really simple. Given the variables described in the 
-  noespec.yaml file (for which values are specified in your .noespec file) templates 
-  can use the following meta-constructions:
-  
-  * Template files and directories containing `__variable__` in their name are automatically
-    renamed (`__variable__` is replaced by the corresponding value).
-  * All template files are instantiated by [wlang](https://github.com/blambeau/wlang). You 
-    don't have to know wlang in depth. You simply have to know that `!{ruby_expression}` in 
-    a file is replaced by the expression evaluation. Variables are automatically in scope 
-    of such expressions, so that `!{variable}` is replaced by its value.
-  
-  ## Contributing
-  
-  Fork Noe on github! I'm particularly interested in the following enhancements:
-  
-  * Extend test coverage, which is ugly so far.
-  * Enhance the default ruby template, but remember "documentation matters, not magic!"
-  * Add support for other generators than _wlang_
-  * Add support for multi-generated files from arrays in .noespec files
-  * ...
-  
-  If you think that your template is worth considering for (ruby, rails, js, latex, or 
-  anything else) please let me known and I'll add it to the list below.
-  
-  * ...
-
+  requirement: *id009
+description: Noe is a tool that generates project skeletons from predefined templates. A template is designed for a specific product (a ruby library, a static or dynamic web site, ...). Noe instantiates templates and helps you maintaining your product via meta-information provided by a .noespec yaml file. In contrast to other tools, Noe is not specific to certain kinds of products. Writing your own template is possible and even simple!
 email: 
 - blambeau@gmail.com
 executables: 
@@ -341,10 +173,10 @@ extra_rdoc_files:
 - CHANGELOG.md
 - LICENCE.md
 files: 
-- ./noe.gemspec
+- ./bin/noe
 - ./CHANGELOG.md
 - ./Gemfile
-- ./bin/noe
+- ./Gemfile.lock
 - ./lib/noe/commons.rb
 - ./lib/noe/config.rb
 - ./lib/noe/config.yaml
@@ -361,6 +193,9 @@ files:
 - ./lib/noe/template.rb
 - ./lib/noe.rb
 - ./LICENCE.md
+- ./Manifest.txt
+- ./noe.gemspec
+- ./noe.noespec
 - ./Rakefile
 - ./README.md
 - ./spec/ext/hash/methodize_spec.rb
@@ -369,6 +204,8 @@ files:
 - ./spec/template/entry/infer_wlang_dialect_spec.rb
 - ./spec/template/entry/relocate_spec.rb
 - ./spec/template/entry/rename_one_spec.rb
+- ./tasks/debug_mail.rake
+- ./tasks/debug_mail.txt
 - ./tasks/gem.rake
 - ./tasks/spec_test.rake
 - ./tasks/unit_test.rake
@@ -388,6 +225,8 @@ files:
 - ./templates/ruby/src/README.md
 - ./templates/ruby/src/spec/__lower___spec.rb
 - ./templates/ruby/src/spec/spec_helper.rb
+- ./templates/ruby/src/tasks/debug_mail.rake
+- ./templates/ruby/src/tasks/debug_mail.txt
 - ./templates/ruby/src/tasks/gem.rake
 - ./templates/ruby/src/tasks/spec_test.rake
 - ./templates/ruby/src/tasks/unit_test.rake
@@ -443,7 +282,7 @@ rubyforge_project:
 rubygems_version: 1.4.2
 signing_key: 
 specification_version: 3
-summary: Noe is a tool that generates projects from predefined skeletons (aka project/application templates). Skeletons are designed for building specific products (a ruby library, a static or dynamic web site, ...). Noe instantiates them and helps you maintaining your product via meta-information provided by a .noespec yaml file.
+summary: Noe is a simple, general-purpose and extensible skeleton generator from project templates
 test_files: 
 - spec/ext/hash/methodize_spec.rb
 - spec/noe_spec.rb