aboutsummaryrefslogtreecommitdiffstats
path: root/guides/source/plugins.md
diff options
context:
space:
mode:
Diffstat (limited to 'guides/source/plugins.md')
-rw-r--r--guides/source/plugins.md9
1 files changed, 3 insertions, 6 deletions
diff --git a/guides/source/plugins.md b/guides/source/plugins.md
index c7c843ec3a..f8f04c3c67 100644
--- a/guides/source/plugins.md
+++ b/guides/source/plugins.md
@@ -9,8 +9,8 @@ A Rails plugin is either an extension or a modification of the core framework. P
After reading this guide, you will know:
-* Creating a plugin from scratch.
-* Writing and running tests for the plugin.
+* How to create a plugin from scratch.
+* How to write and run tests for the plugin.
This guide describes how to build a test-driven plugin that will:
@@ -27,16 +27,13 @@ goodness.
Setup
-----
-_"vendored plugins"_ were available in previous versions of Rails, but they are deprecated in
-Rails 3.2, and will not be available in the future.
-
Currently, Rails plugins are built as gems, _gemified plugins_. They can be shared across
different rails applications using RubyGems and Bundler if desired.
### Generate a gemified plugin.
-Rails 3.1 ships with a `rails plugin new` command which creates a
+Rails ships with a `rails plugin new` command which creates a
skeleton for developing any kind of Rails extension with the ability
to run integration tests using a dummy Rails application. See usage
and options by asking for help: