Removing obsolete instructions for releasing.
Cucumber features work correctly now.
[#3] Make use of the Asset Pipeline

BrowserCMS now uses the Rails 3.1 Asset pipeline to serve it's javascript, images and stylesheets for core files.

* Moved CSS to assets folder. Internal CMS templates now use the cms/application.css
* Moved core CMS images to Assets directory.
* Added dependency on jquery-rails
* Moved all JS to asset pipeline.
* Make cms/application.js into a pure manifest file.
* CKEditor now loads through Asset Pipeline and is configurable by gems.
* Moved external jquery libraries (cookie and selectbox) to vendor, since they are external dependencies.
* Deleted rails.js since that's no longer used (jquery-ujs is used via asset pipeline now)
* Removed (broken) bespin editor from dynamic portlets.
* [#443] Removed require_javascript_include and require_stylesheet_link from project (Use asset pipeline instead).
Removed unnecessary call to serve static assets (asset pipeline handles that)
[#446] Redirects are now 301 responses

Changed the default behavior to make redirects a more SEO friendly 301 rather than 302 response. Also updated core project to test against Rails 2.3.11
Release 3.1.4
[#448] Make BrowserCMS a Mountable Engine

Reworked the entire project so it works as an isolated mountable engine. Rather than using paths like cms_dashboard_path, within the engine users can call _dashboard_ and from outside they can call cms.dashboard_path.

Includes the following updates:

* Regenerated project files to use a test/dummy application, like a typical engine would.
* Changed most of the paths so they aren't namespaced via convention (i.e. no more cms_dashboard_path)
* Completely removed all fixtures in favor of FactoryGirl
* Updated unit/functional tests to use new path patterns as well as factories.
* Started the process of replacing functional and integration with Cucumber features (both for improved documentation and fixing brittle tests)
* Improve cucumber coverage of more areas of the admin site.
* Moving config (like initializers) and other testing code (like sample controllers) may help solve [#416] which should allow bcms to be specified in a Gemfile using :git=> syntax
* Removed the namespacing of attributes on forms (i.e params[:html_block] rather than params[:cms_html_block])
* Added new method for adding the bcms routes to a project (mount_browsercms rather than routes_for_browser_cms). Old method is deprecated, and new projects will be generated with the new syntax.
Updated gemspec to automatically find files using git
[#416] Add browsercms to Gemfiles via :git

Confirmed that changes for #448 allow BrowserCMS to be added to project using :git rather than released gem.
[#446] 301 Redirects

Merging this from 3.1.x branch into master.
Merge 3.3.x into master.
Match Rails 3.1 default config options. XSendfile and serve_static_assets can remain disabled.
Removed bespin editor features

This was accidently merged in as part of the namespacing commits and was not working with Rails 3.1. Having this is desirable, but it should be a separate module probably.
Remove selenium tests since they were way out of date and better handled via cucumber instead.
Remove unnecessary static files from the gem, since rails will generate these as needed for projects.
Since FCKeditor is no longer the default, remove the custom config.js from the project.
More public directory cleanup
Updating todo list.
[Ruby 1.9.3] Upgrade to work w/ Ruby 1.9.3

* Use mysql2 v0.3.10 gem - Fixes issues with Lion/Ruby 1.9.3 bugs.
* Setup the test database automatically each time `rake test` is run.
* Fix issue with where temp files were written out as absolute paths.
* Write todo plan for 3.4 release.
Differ `bundle install` from happening until after browsercms has been added.