reap 6.0.2 → 9.2.0

data/bin/reap-scm-tag

@@ -0,0 +1,7 @@
+#!/usr/bin/env ruby
+
+require 'reap/application'
+
+app = Reap::Application.new
+
+app.scm_tag

data/bin/reap-spec

@@ -0,0 +1,7 @@
+#!/usr/bin/env ruby
+
+require 'reap/application'
+
+app = Reap::Application.new
+
+app.spec

data/bin/reap-spec-doc

@@ -0,0 +1,8 @@
+#!/usr/bin/env ruby
+
+require 'reap/application'
+
+app = Reap::Application.new
+
+app.spec_doc
+

data/bin/reap-stamp

@@ -0,0 +1,7 @@
+#!/usr/bin/env ruby
+
+require 'reap/application'
+
+app = Reap::Application.new
+
+app.stamp

data/bin/reap-stats

@@ -0,0 +1,7 @@
+#!/usr/bin/env ruby
+
+require 'reap/application'
+
+app = Reap::Application.new
+
+app.stats

data/bin/reap-test

@@ -0,0 +1,7 @@
+#!/usr/bin/env ruby
+
+require 'reap/application'
+
+app = Reap::Application.new
+
+app.test_unit

data/bin/reap-test-cross

@@ -0,0 +1,7 @@
+#!/usr/bin/env ruby
+
+require 'reap/application'
+
+app = Reap::Application.new
+
+app.test_cross

data/bin/reap-test-load

@@ -0,0 +1,9 @@
+#!/usr/bin/env ruby
+
+# Ensure all unit tests load properly.
+
+require 'reap/application'
+
+app = Reap::Application.new
+
+app.test_load

data/bin/reap-test-solo

@@ -0,0 +1,7 @@
+#!/usr/bin/env ruby
+
+require 'reap/application'
+
+app = Reap::Application.new
+
+app.test_solo

data/bin/reap-uninstall

@@ -0,0 +1,7 @@
+#!/usr/bin/env ruby
+
+require 'reap/application'
+
+app = Reap::Application.new
+
+app.site_uninstall

data/bin/reap-uninstall-gem

@@ -0,0 +1,7 @@
+#!/usr/bin/env ruby
+
+require 'reap/application'
+
+app = Reap::Application.new
+
+app.gem_uninstall

data/data/reap/base/CHANGES

@@ -0,0 +1,19 @@
+== 0.0.0 // 2008-03-04
+
+* Started project.
+
+
+
+# NOTE:
+#
+#   Keep a running list of changes by version and date here.
+#   This is uploaded as the ChangeLog in the release process.
+#   It's better to keep a manual log, rather then use the log
+#   generated by the SCM because the SCM log will have gritty
+#   details with which end-users will not be concerned.
+#
+#   If you want to use the SCM log anyway, you can of course
+#   do so. Just "cp log/Changelog.txt CHANGES" prior to release.
+#   (We might provide an automated option for this in the
+#   future, but for now its a manual task.)
+