deprecate guard-jammit

README.md

@@ -15,10 +15,15 @@ home folder's `.jasmine-headless-webkit` file.
 ## `guard` options
 
 * `:all_on_start => false` to not run everything when starting, just like `guard-rspec`.
-* `:run_before => "<command to run>` to run a command before running specs. If the command fails, the test run stops.
-* `:jammit => true` to run `jammit -f 2>/dev/null` before the tests for the current file change are run.
+* `:rails_assets => true` to repackage Rails assets before each run.
+* `:run_before => "<command to run>"` to run a command before running specs. If the command fails, the test run stops.
 * `:valid_extensions => %w{js coffee}` to only trigger `run_on_change` events for files with these extensions. Forces Guard to re-run all tests when any other matched file changes.
 
+### Deprecated options
+
+* `:jammit => true` to run `jammit -f 2>/dev/null` before the tests for the current file change are run.
+  * Use [guard-jammit](http://github.com/guard/guard-jammit) instead.
+
 ## What's the deal with `newest_js_file`?
 
 Since one could, theoretically, have a CoffeeScript app file and a JavaScript spec file (or vice versa), the search for the correct matching

lib/guard/jasmine-headless-webkit.rb

@@ -54,6 +54,7 @@ module Guard
     end
 
     def run_jammit
+      $stderr.puts "Jammit support is deprecated and will be removed in the future. Use guard-jammit instead." if @options[:jammit]
       run_a_thing_before(:jammit, "Jammit", %{jammit -f 2>/dev/null})
     end